@meeco/svx-api-sdk 1.0.0-stage.20240502114933.d123429 → 1.0.0-stage.20240624095554.3e253ce

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (62) hide show
  1. package/.openapi-generator/FILES +2 -0
  2. package/lib/esm/apis/ConnectionsApi.js +69 -69
  3. package/lib/esm/apis/HelpersApi.js +14 -8
  4. package/lib/esm/apis/ItemsApi.js +24 -24
  5. package/lib/esm/apis/OrganisationsApi.js +176 -176
  6. package/lib/esm/apis/SecurityRightsApi.js +80 -80
  7. package/lib/esm/apis/SharesApi.js +24 -24
  8. package/lib/esm/apis/TenantsApi.js +174 -174
  9. package/lib/esm/apis/VerifiableCredentialsApi.js +12 -6
  10. package/lib/esm/apis/VerifiablePresentationsApi.js +1 -0
  11. package/lib/esm/models/ATOMBlobInfo.js +8 -0
  12. package/lib/esm/models/ATOMBlobPublicInfo.js +6 -0
  13. package/lib/esm/models/ATOMFileStorageBackend.js +45 -0
  14. package/lib/esm/models/ATOMFileStorageConfiguration.js +46 -0
  15. package/lib/esm/models/VCCredentialTypeModelDtoSchema.js +6 -0
  16. package/lib/esm/models/VCCredentialTypeSchemaDto.js +6 -0
  17. package/lib/esm/models/VCInputDescriptorsDto.js +3 -0
  18. package/lib/esm/models/VCPresentationDefinitionDto.js +0 -3
  19. package/lib/esm/models/VCPresentationDefinitionToSchemaModel.js +3 -0
  20. package/lib/esm/models/VCVerifyPresentationRequestResponseDto.js +3 -2
  21. package/lib/esm/models/index.js +2 -0
  22. package/lib/types/apis/ConnectionsApi.d.ts +36 -36
  23. package/lib/types/apis/HelpersApi.d.ts +8 -7
  24. package/lib/types/apis/ItemsApi.d.ts +18 -18
  25. package/lib/types/apis/OrganisationsApi.d.ts +82 -82
  26. package/lib/types/apis/SecurityRightsApi.d.ts +28 -28
  27. package/lib/types/apis/SharesApi.d.ts +16 -16
  28. package/lib/types/apis/TenantsApi.d.ts +82 -82
  29. package/lib/types/apis/VerifiableCredentialsApi.d.ts +6 -4
  30. package/lib/types/apis/VerifiablePresentationsApi.d.ts +1 -0
  31. package/lib/types/models/ATOMBlobInfo.d.ts +18 -0
  32. package/lib/types/models/ATOMBlobPublicInfo.d.ts +12 -0
  33. package/lib/types/models/ATOMFileStorageBackend.d.ts +37 -0
  34. package/lib/types/models/ATOMFileStorageConfiguration.d.ts +38 -0
  35. package/lib/types/models/VCCredentialTypeModelDtoSchema.d.ts +12 -0
  36. package/lib/types/models/VCCredentialTypeSchemaDto.d.ts +12 -0
  37. package/lib/types/models/VCInputDescriptorsDto.d.ts +7 -0
  38. package/lib/types/models/VCPresentationDefinitionDto.d.ts +0 -7
  39. package/lib/types/models/VCPresentationDefinitionToSchemaModel.d.ts +6 -0
  40. package/lib/types/models/VCVerifyPresentationRequestResponseDto.d.ts +7 -1
  41. package/lib/types/models/index.d.ts +2 -0
  42. package/lib/umd/apis/ConnectionsApi.js +69 -69
  43. package/lib/umd/apis/HelpersApi.js +14 -8
  44. package/lib/umd/apis/ItemsApi.js +24 -24
  45. package/lib/umd/apis/OrganisationsApi.js +176 -176
  46. package/lib/umd/apis/SecurityRightsApi.js +80 -80
  47. package/lib/umd/apis/SharesApi.js +24 -24
  48. package/lib/umd/apis/TenantsApi.js +174 -174
  49. package/lib/umd/apis/VerifiableCredentialsApi.js +12 -6
  50. package/lib/umd/apis/VerifiablePresentationsApi.js +1 -0
  51. package/lib/umd/models/ATOMBlobInfo.js +8 -0
  52. package/lib/umd/models/ATOMBlobPublicInfo.js +6 -0
  53. package/lib/umd/models/ATOMFileStorageBackend.js +52 -0
  54. package/lib/umd/models/ATOMFileStorageConfiguration.js +53 -0
  55. package/lib/umd/models/VCCredentialTypeModelDtoSchema.js +6 -0
  56. package/lib/umd/models/VCCredentialTypeSchemaDto.js +6 -0
  57. package/lib/umd/models/VCInputDescriptorsDto.js +3 -0
  58. package/lib/umd/models/VCPresentationDefinitionDto.js +0 -3
  59. package/lib/umd/models/VCPresentationDefinitionToSchemaModel.js +3 -0
  60. package/lib/umd/models/VCVerifyPresentationRequestResponseDto.js +3 -2
  61. package/lib/umd/models/index.js +2 -0
  62. package/package.json +1 -1
@@ -35,6 +35,8 @@ models/ATOMComponent.ts
35
35
  models/ATOMCreateOrUpdateOrgRequest.ts
36
36
  models/ATOMCreateOrUpdateTenantRequest.ts
37
37
  models/ATOMError.ts
38
+ models/ATOMFileStorageBackend.ts
39
+ models/ATOMFileStorageConfiguration.ts
38
40
  models/ATOMGenesisRequest.ts
39
41
  models/ATOMNewAgentRequest.ts
40
42
  models/ATOMOneAgent.ts
@@ -254,16 +254,17 @@ export class ConnectionsApi extends runtime.BaseAPI {
254
254
  });
255
255
  }
256
256
  /**
257
- * Delete an invitation by its token or ID. Only the user who created the invitation may delete it.
258
- * Delete an invitation
257
+ * Accept an invitation. This endpoint is only available if the multistep invitation flow is enabled. Accepting an endpoint does not create a connection. After an invitation is accepted, the sender of the invitation needs to confirm it. --- If there is already a connection between these two users, then * the response will contain the existing connection * field `invitation` will be set to `NULL` * field `connection_existed_already` will be set to `true` * any share intents attached to the invitation will be used to create shares
258
+ * Accept an invitation
259
259
  */
260
- invitationsIdDeleteRaw(requestParameters, initOverrides) {
260
+ invitationsInvitationIdAcceptPostRaw(requestParameters, initOverrides) {
261
261
  return __awaiter(this, void 0, void 0, function* () {
262
- if (requestParameters.id === null || requestParameters.id === undefined) {
263
- throw new runtime.RequiredError('id', 'Required parameter requestParameters.id was null or undefined when calling invitationsIdDelete.');
262
+ if (requestParameters.invitationId === null || requestParameters.invitationId === undefined) {
263
+ throw new runtime.RequiredError('invitationId', 'Required parameter requestParameters.invitationId was null or undefined when calling invitationsInvitationIdAcceptPost.');
264
264
  }
265
265
  const queryParameters = {};
266
266
  const headerParameters = {};
267
+ headerParameters['Content-Type'] = 'application/json';
267
268
  if (requestParameters.meecoDelegationId !== undefined && requestParameters.meecoDelegationId !== null) {
268
269
  headerParameters['Meeco-Delegation-Id'] = String(requestParameters.meecoDelegationId);
269
270
  }
@@ -278,31 +279,33 @@ export class ConnectionsApi extends runtime.BaseAPI {
278
279
  }
279
280
  }
280
281
  const response = yield this.request({
281
- path: `/invitations/{id}`.replace(`{${"id"}}`, encodeURIComponent(String(requestParameters.id))),
282
- method: 'DELETE',
282
+ path: `/invitations/{invitation_id}/accept`.replace(`{${"invitation_id"}}`, encodeURIComponent(String(requestParameters.invitationId))),
283
+ method: 'POST',
283
284
  headers: headerParameters,
284
285
  query: queryParameters,
286
+ body: AcceptInvitationsRequestToJSON(requestParameters.acceptInvitationsRequest),
285
287
  }, initOverrides);
286
- return new runtime.VoidApiResponse(response);
288
+ return new runtime.JSONApiResponse(response, (jsonValue) => VaultInvitationAcceptedResponseFromJSON(jsonValue));
287
289
  });
288
290
  }
289
291
  /**
290
- * Delete an invitation by its token or ID. Only the user who created the invitation may delete it.
291
- * Delete an invitation
292
+ * Accept an invitation. This endpoint is only available if the multistep invitation flow is enabled. Accepting an endpoint does not create a connection. After an invitation is accepted, the sender of the invitation needs to confirm it. --- If there is already a connection between these two users, then * the response will contain the existing connection * field `invitation` will be set to `NULL` * field `connection_existed_already` will be set to `true` * any share intents attached to the invitation will be used to create shares
293
+ * Accept an invitation
292
294
  */
293
- invitationsIdDelete(id, meecoDelegationId, meecoOrganisationId, initOverrides) {
295
+ invitationsInvitationIdAcceptPost(invitationId, meecoDelegationId, meecoOrganisationId, acceptInvitationsRequest, initOverrides) {
294
296
  return __awaiter(this, void 0, void 0, function* () {
295
- yield this.invitationsIdDeleteRaw({ id: id, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
297
+ const response = yield this.invitationsInvitationIdAcceptPostRaw({ invitationId: invitationId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId, acceptInvitationsRequest: acceptInvitationsRequest }, initOverrides);
298
+ return yield response.value();
296
299
  });
297
300
  }
298
301
  /**
299
- * Read an invitation by its token or ID. Can be used by both the invitation sender, and someone with an invitation token.Fields `id` and `keypair_external_id` are NULL if the current user is not the sender of the invitation
300
- * Read an invitation
302
+ * Reject an accepted invitation. This endpoint is only available if the multistep invitation flow is enabled. First an invitation recipient accepts an an invitation is accepted, and then the sender of the invitation can reject it using this endpoint. Only the sender of the invitation can call this endpoint.
303
+ * Reject an accepted invitation
301
304
  */
302
- invitationsIdGetRaw(requestParameters, initOverrides) {
305
+ invitationsInvitationIdCancelDeleteRaw(requestParameters, initOverrides) {
303
306
  return __awaiter(this, void 0, void 0, function* () {
304
- if (requestParameters.id === null || requestParameters.id === undefined) {
305
- throw new runtime.RequiredError('id', 'Required parameter requestParameters.id was null or undefined when calling invitationsIdGet.');
307
+ if (requestParameters.invitationId === null || requestParameters.invitationId === undefined) {
308
+ throw new runtime.RequiredError('invitationId', 'Required parameter requestParameters.invitationId was null or undefined when calling invitationsInvitationIdCancelDelete.');
306
309
  }
307
310
  const queryParameters = {};
308
311
  const headerParameters = {};
@@ -320,35 +323,36 @@ export class ConnectionsApi extends runtime.BaseAPI {
320
323
  }
321
324
  }
322
325
  const response = yield this.request({
323
- path: `/invitations/{id}`.replace(`{${"id"}}`, encodeURIComponent(String(requestParameters.id))),
324
- method: 'GET',
326
+ path: `/invitations/{invitation_id}/cancel`.replace(`{${"invitation_id"}}`, encodeURIComponent(String(requestParameters.invitationId))),
327
+ method: 'DELETE',
325
328
  headers: headerParameters,
326
329
  query: queryParameters,
327
330
  }, initOverrides);
328
- return new runtime.JSONApiResponse(response, (jsonValue) => InvitationWithShareIntentsResponseFromJSON(jsonValue));
331
+ return new runtime.JSONApiResponse(response, (jsonValue) => InvitationResponseFromJSON(jsonValue));
329
332
  });
330
333
  }
331
334
  /**
332
- * Read an invitation by its token or ID. Can be used by both the invitation sender, and someone with an invitation token.Fields `id` and `keypair_external_id` are NULL if the current user is not the sender of the invitation
333
- * Read an invitation
335
+ * Reject an accepted invitation. This endpoint is only available if the multistep invitation flow is enabled. First an invitation recipient accepts an an invitation is accepted, and then the sender of the invitation can reject it using this endpoint. Only the sender of the invitation can call this endpoint.
336
+ * Reject an accepted invitation
334
337
  */
335
- invitationsIdGet(id, meecoDelegationId, meecoOrganisationId, initOverrides) {
338
+ invitationsInvitationIdCancelDelete(invitationId, meecoDelegationId, meecoOrganisationId, initOverrides) {
336
339
  return __awaiter(this, void 0, void 0, function* () {
337
- const response = yield this.invitationsIdGetRaw({ id: id, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
340
+ const response = yield this.invitationsInvitationIdCancelDeleteRaw({ invitationId: invitationId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
338
341
  return yield response.value();
339
342
  });
340
343
  }
341
344
  /**
342
- * Reject an accepted invitation. This endpoint is only available if the multistep invitation flow is enabled. First an invitation recipient accepts an an invitation is accepted, and then the sender of the invitation can reject it using this endpoint. Only the sender of the invitation can call this endpoint.
343
- * Reject an accepted invitation
345
+ * Confirm an accepted invitation. This endpoint is only available if the multistep invitation flow is enabled. First an invitation recipient accepts an an invitation is accepted, and then the sender of the invitation can confirm it using this endpoint. Only the sender of the invitation can call this endpoint.Parameter `encrypted_dek` is used for share intents in the multistep invitation workflow. In the multistep invitation workflow when share intents are created, they are first encrypted with the private DEK on the invitation sender. At this confirmation step the sender of the invitation already has access to the public key of the recipient in the invitation, field `recipient_public_key`, and the sender of the invitation is expected to re-encrypt the DEK in the share intents with the public key of the recipient. `encrypted_dek` is mandatory if there are share intents. --- If there is already a connection between these two users, then * the response will contain the existing connection * field `invitation` will be set to `NULL` * field `connection_existed_already` will be set to `true` * any share intents attached to the invitation will be used to create shares
346
+ * Confirm an accepted invitation
344
347
  */
345
- invitationsInvitationIdCancelDeleteRaw(requestParameters, initOverrides) {
348
+ invitationsInvitationIdConfirmPostRaw(requestParameters, initOverrides) {
346
349
  return __awaiter(this, void 0, void 0, function* () {
347
350
  if (requestParameters.invitationId === null || requestParameters.invitationId === undefined) {
348
- throw new runtime.RequiredError('invitationId', 'Required parameter requestParameters.invitationId was null or undefined when calling invitationsInvitationIdCancelDelete.');
351
+ throw new runtime.RequiredError('invitationId', 'Required parameter requestParameters.invitationId was null or undefined when calling invitationsInvitationIdConfirmPost.');
349
352
  }
350
353
  const queryParameters = {};
351
354
  const headerParameters = {};
355
+ headerParameters['Content-Type'] = 'application/json';
352
356
  if (requestParameters.meecoDelegationId !== undefined && requestParameters.meecoDelegationId !== null) {
353
357
  headerParameters['Meeco-Delegation-Id'] = String(requestParameters.meecoDelegationId);
354
358
  }
@@ -363,36 +367,36 @@ export class ConnectionsApi extends runtime.BaseAPI {
363
367
  }
364
368
  }
365
369
  const response = yield this.request({
366
- path: `/invitations/{invitation_id}/cancel`.replace(`{${"invitation_id"}}`, encodeURIComponent(String(requestParameters.invitationId))),
367
- method: 'DELETE',
370
+ path: `/invitations/{invitation_id}/confirm`.replace(`{${"invitation_id"}}`, encodeURIComponent(String(requestParameters.invitationId))),
371
+ method: 'POST',
368
372
  headers: headerParameters,
369
373
  query: queryParameters,
374
+ body: AcceptInvitationsRequest1ToJSON(requestParameters.acceptInvitationsRequest1),
370
375
  }, initOverrides);
371
- return new runtime.JSONApiResponse(response, (jsonValue) => InvitationResponseFromJSON(jsonValue));
376
+ return new runtime.JSONApiResponse(response, (jsonValue) => VaultInvitationAcceptedResponseFromJSON(jsonValue));
372
377
  });
373
378
  }
374
379
  /**
375
- * Reject an accepted invitation. This endpoint is only available if the multistep invitation flow is enabled. First an invitation recipient accepts an an invitation is accepted, and then the sender of the invitation can reject it using this endpoint. Only the sender of the invitation can call this endpoint.
376
- * Reject an accepted invitation
380
+ * Confirm an accepted invitation. This endpoint is only available if the multistep invitation flow is enabled. First an invitation recipient accepts an an invitation is accepted, and then the sender of the invitation can confirm it using this endpoint. Only the sender of the invitation can call this endpoint.Parameter `encrypted_dek` is used for share intents in the multistep invitation workflow. In the multistep invitation workflow when share intents are created, they are first encrypted with the private DEK on the invitation sender. At this confirmation step the sender of the invitation already has access to the public key of the recipient in the invitation, field `recipient_public_key`, and the sender of the invitation is expected to re-encrypt the DEK in the share intents with the public key of the recipient. `encrypted_dek` is mandatory if there are share intents. --- If there is already a connection between these two users, then * the response will contain the existing connection * field `invitation` will be set to `NULL` * field `connection_existed_already` will be set to `true` * any share intents attached to the invitation will be used to create shares
381
+ * Confirm an accepted invitation
377
382
  */
378
- invitationsInvitationIdCancelDelete(invitationId, meecoDelegationId, meecoOrganisationId, initOverrides) {
383
+ invitationsInvitationIdConfirmPost(invitationId, meecoDelegationId, meecoOrganisationId, acceptInvitationsRequest1, initOverrides) {
379
384
  return __awaiter(this, void 0, void 0, function* () {
380
- const response = yield this.invitationsInvitationIdCancelDeleteRaw({ invitationId: invitationId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
385
+ const response = yield this.invitationsInvitationIdConfirmPostRaw({ invitationId: invitationId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId, acceptInvitationsRequest1: acceptInvitationsRequest1 }, initOverrides);
381
386
  return yield response.value();
382
387
  });
383
388
  }
384
389
  /**
385
- * Confirm an accepted invitation. This endpoint is only available if the multistep invitation flow is enabled. First an invitation recipient accepts an an invitation is accepted, and then the sender of the invitation can confirm it using this endpoint. Only the sender of the invitation can call this endpoint.Parameter `encrypted_dek` is used for share intents in the multistep invitation workflow. In the multistep invitation workflow when share intents are created, they are first encrypted with the private DEK on the invitation sender. At this confirmation step the sender of the invitation already has access to the public key of the recipient in the invitation, field `recipient_public_key`, and the sender of the invitation is expected to re-encrypt the DEK in the share intents with the public key of the recipient. `encrypted_dek` is mandatory if there are share intents. --- If there is already a connection between these two users, then * the response will contain the existing connection * field `invitation` will be set to `NULL` * field `connection_existed_already` will be set to `true` * any share intents attached to the invitation will be used to create shares
386
- * Confirm an accepted invitation
390
+ * Delete an invitation by its token or ID. Only the user who created the invitation may delete it.
391
+ * Delete an invitation
387
392
  */
388
- invitationsInvitationIdConfirmPostRaw(requestParameters, initOverrides) {
393
+ invitationsInvitationIdDeleteRaw(requestParameters, initOverrides) {
389
394
  return __awaiter(this, void 0, void 0, function* () {
390
395
  if (requestParameters.invitationId === null || requestParameters.invitationId === undefined) {
391
- throw new runtime.RequiredError('invitationId', 'Required parameter requestParameters.invitationId was null or undefined when calling invitationsInvitationIdConfirmPost.');
396
+ throw new runtime.RequiredError('invitationId', 'Required parameter requestParameters.invitationId was null or undefined when calling invitationsInvitationIdDelete.');
392
397
  }
393
398
  const queryParameters = {};
394
399
  const headerParameters = {};
395
- headerParameters['Content-Type'] = 'application/json';
396
400
  if (requestParameters.meecoDelegationId !== undefined && requestParameters.meecoDelegationId !== null) {
397
401
  headerParameters['Meeco-Delegation-Id'] = String(requestParameters.meecoDelegationId);
398
402
  }
@@ -407,37 +411,34 @@ export class ConnectionsApi extends runtime.BaseAPI {
407
411
  }
408
412
  }
409
413
  const response = yield this.request({
410
- path: `/invitations/{invitation_id}/confirm`.replace(`{${"invitation_id"}}`, encodeURIComponent(String(requestParameters.invitationId))),
411
- method: 'POST',
414
+ path: `/invitations/{invitation_id}`.replace(`{${"invitation_id"}}`, encodeURIComponent(String(requestParameters.invitationId))),
415
+ method: 'DELETE',
412
416
  headers: headerParameters,
413
417
  query: queryParameters,
414
- body: AcceptInvitationsRequest1ToJSON(requestParameters.acceptInvitationsRequest1),
415
418
  }, initOverrides);
416
- return new runtime.JSONApiResponse(response, (jsonValue) => VaultInvitationAcceptedResponseFromJSON(jsonValue));
419
+ return new runtime.VoidApiResponse(response);
417
420
  });
418
421
  }
419
422
  /**
420
- * Confirm an accepted invitation. This endpoint is only available if the multistep invitation flow is enabled. First an invitation recipient accepts an an invitation is accepted, and then the sender of the invitation can confirm it using this endpoint. Only the sender of the invitation can call this endpoint.Parameter `encrypted_dek` is used for share intents in the multistep invitation workflow. In the multistep invitation workflow when share intents are created, they are first encrypted with the private DEK on the invitation sender. At this confirmation step the sender of the invitation already has access to the public key of the recipient in the invitation, field `recipient_public_key`, and the sender of the invitation is expected to re-encrypt the DEK in the share intents with the public key of the recipient. `encrypted_dek` is mandatory if there are share intents. --- If there is already a connection between these two users, then * the response will contain the existing connection * field `invitation` will be set to `NULL` * field `connection_existed_already` will be set to `true` * any share intents attached to the invitation will be used to create shares
421
- * Confirm an accepted invitation
423
+ * Delete an invitation by its token or ID. Only the user who created the invitation may delete it.
424
+ * Delete an invitation
422
425
  */
423
- invitationsInvitationIdConfirmPost(invitationId, meecoDelegationId, meecoOrganisationId, acceptInvitationsRequest1, initOverrides) {
426
+ invitationsInvitationIdDelete(invitationId, meecoDelegationId, meecoOrganisationId, initOverrides) {
424
427
  return __awaiter(this, void 0, void 0, function* () {
425
- const response = yield this.invitationsInvitationIdConfirmPostRaw({ invitationId: invitationId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId, acceptInvitationsRequest1: acceptInvitationsRequest1 }, initOverrides);
426
- return yield response.value();
428
+ yield this.invitationsInvitationIdDeleteRaw({ invitationId: invitationId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
427
429
  });
428
430
  }
429
431
  /**
430
- * Accept an invitation. This endpoint is only available if the multistep invitation flow is enabled. Accepting an endpoint does not create a connection. After an invitation is accepted, the sender of the invitation needs to confirm it. --- If there is already a connection between these two users, then * the response will contain the existing connection * field `invitation` will be set to `NULL` * field `connection_existed_already` will be set to `true` * any share intents attached to the invitation will be used to create shares
431
- * Accept an invitation
432
+ * Read an invitation by its token or ID. Can be used by both the invitation sender, and someone with an invitation token.Fields `id` and `keypair_external_id` are NULL if the current user is not the sender of the invitation
433
+ * Read an invitation
432
434
  */
433
- invitationsInvitationTokenAcceptPostRaw(requestParameters, initOverrides) {
435
+ invitationsInvitationIdGetRaw(requestParameters, initOverrides) {
434
436
  return __awaiter(this, void 0, void 0, function* () {
435
- if (requestParameters.invitationToken === null || requestParameters.invitationToken === undefined) {
436
- throw new runtime.RequiredError('invitationToken', 'Required parameter requestParameters.invitationToken was null or undefined when calling invitationsInvitationTokenAcceptPost.');
437
+ if (requestParameters.invitationId === null || requestParameters.invitationId === undefined) {
438
+ throw new runtime.RequiredError('invitationId', 'Required parameter requestParameters.invitationId was null or undefined when calling invitationsInvitationIdGet.');
437
439
  }
438
440
  const queryParameters = {};
439
441
  const headerParameters = {};
440
- headerParameters['Content-Type'] = 'application/json';
441
442
  if (requestParameters.meecoDelegationId !== undefined && requestParameters.meecoDelegationId !== null) {
442
443
  headerParameters['Meeco-Delegation-Id'] = String(requestParameters.meecoDelegationId);
443
444
  }
@@ -452,22 +453,21 @@ export class ConnectionsApi extends runtime.BaseAPI {
452
453
  }
453
454
  }
454
455
  const response = yield this.request({
455
- path: `/invitations/{invitation_token}/accept`.replace(`{${"invitation_token"}}`, encodeURIComponent(String(requestParameters.invitationToken))),
456
- method: 'POST',
456
+ path: `/invitations/{invitation_id}`.replace(`{${"invitation_id"}}`, encodeURIComponent(String(requestParameters.invitationId))),
457
+ method: 'GET',
457
458
  headers: headerParameters,
458
459
  query: queryParameters,
459
- body: AcceptInvitationsRequestToJSON(requestParameters.acceptInvitationsRequest),
460
460
  }, initOverrides);
461
- return new runtime.JSONApiResponse(response, (jsonValue) => VaultInvitationAcceptedResponseFromJSON(jsonValue));
461
+ return new runtime.JSONApiResponse(response, (jsonValue) => InvitationWithShareIntentsResponseFromJSON(jsonValue));
462
462
  });
463
463
  }
464
464
  /**
465
- * Accept an invitation. This endpoint is only available if the multistep invitation flow is enabled. Accepting an endpoint does not create a connection. After an invitation is accepted, the sender of the invitation needs to confirm it. --- If there is already a connection between these two users, then * the response will contain the existing connection * field `invitation` will be set to `NULL` * field `connection_existed_already` will be set to `true` * any share intents attached to the invitation will be used to create shares
466
- * Accept an invitation
465
+ * Read an invitation by its token or ID. Can be used by both the invitation sender, and someone with an invitation token.Fields `id` and `keypair_external_id` are NULL if the current user is not the sender of the invitation
466
+ * Read an invitation
467
467
  */
468
- invitationsInvitationTokenAcceptPost(invitationToken, meecoDelegationId, meecoOrganisationId, acceptInvitationsRequest, initOverrides) {
468
+ invitationsInvitationIdGet(invitationId, meecoDelegationId, meecoOrganisationId, initOverrides) {
469
469
  return __awaiter(this, void 0, void 0, function* () {
470
- const response = yield this.invitationsInvitationTokenAcceptPostRaw({ invitationToken: invitationToken, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId, acceptInvitationsRequest: acceptInvitationsRequest }, initOverrides);
470
+ const response = yield this.invitationsInvitationIdGetRaw({ invitationId: invitationId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
471
471
  return yield response.value();
472
472
  });
473
473
  }
@@ -475,10 +475,10 @@ export class ConnectionsApi extends runtime.BaseAPI {
475
475
  * Reject an invitation. This endpoint is only available if the multistep invitation flow is enabled.
476
476
  * Reject an invitation
477
477
  */
478
- invitationsInvitationTokenRejectDeleteRaw(requestParameters, initOverrides) {
478
+ invitationsInvitationIdRejectDeleteRaw(requestParameters, initOverrides) {
479
479
  return __awaiter(this, void 0, void 0, function* () {
480
- if (requestParameters.invitationToken === null || requestParameters.invitationToken === undefined) {
481
- throw new runtime.RequiredError('invitationToken', 'Required parameter requestParameters.invitationToken was null or undefined when calling invitationsInvitationTokenRejectDelete.');
480
+ if (requestParameters.invitationId === null || requestParameters.invitationId === undefined) {
481
+ throw new runtime.RequiredError('invitationId', 'Required parameter requestParameters.invitationId was null or undefined when calling invitationsInvitationIdRejectDelete.');
482
482
  }
483
483
  const queryParameters = {};
484
484
  const headerParameters = {};
@@ -496,7 +496,7 @@ export class ConnectionsApi extends runtime.BaseAPI {
496
496
  }
497
497
  }
498
498
  const response = yield this.request({
499
- path: `/invitations/{invitation_token}/reject`.replace(`{${"invitation_token"}}`, encodeURIComponent(String(requestParameters.invitationToken))),
499
+ path: `/invitations/{invitation_id}/reject`.replace(`{${"invitation_id"}}`, encodeURIComponent(String(requestParameters.invitationId))),
500
500
  method: 'DELETE',
501
501
  headers: headerParameters,
502
502
  query: queryParameters,
@@ -508,9 +508,9 @@ export class ConnectionsApi extends runtime.BaseAPI {
508
508
  * Reject an invitation. This endpoint is only available if the multistep invitation flow is enabled.
509
509
  * Reject an invitation
510
510
  */
511
- invitationsInvitationTokenRejectDelete(invitationToken, meecoDelegationId, meecoOrganisationId, initOverrides) {
511
+ invitationsInvitationIdRejectDelete(invitationId, meecoDelegationId, meecoOrganisationId, initOverrides) {
512
512
  return __awaiter(this, void 0, void 0, function* () {
513
- const response = yield this.invitationsInvitationTokenRejectDeleteRaw({ invitationToken: invitationToken, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
513
+ const response = yield this.invitationsInvitationIdRejectDeleteRaw({ invitationId: invitationId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
514
514
  return yield response.value();
515
515
  });
516
516
  }
@@ -27,8 +27,8 @@ import { ATOMBlobInfoResponseFromJSON, ATOMBlobPublicInfoResponseFromJSON, ATOMB
27
27
  */
28
28
  export class HelpersApi extends runtime.BaseAPI {
29
29
  /**
30
- * Redirect to a file in Azure Blob Storage. This endpoint is public and it only requires the file key in the URL. The `Content Disposition` header in the response is hardcoded to be `inline` for now, but it can be made a parameter to this endpoint in future if needed. The filename and the content type included in `Content Disposition` are taken from the database record created in `POST /blobs`.\"
31
- * Redirect to a file in Azure Blob Storage
30
+ * Redirect to a file in a cloud file storage. This endpoint is public and it only requires the file key in the URL. The `Content Disposition` header in the response is hardcoded to be `inline` for now, but it can be made a parameter to this endpoint in future if needed. The filename and the content type included in `Content Disposition` are taken from the database record created in `POST /blobs`.\"
31
+ * Redirect to a file in a cloud file storage
32
32
  */
33
33
  blobsIdGetRaw(requestParameters, initOverrides) {
34
34
  return __awaiter(this, void 0, void 0, function* () {
@@ -47,8 +47,8 @@ export class HelpersApi extends runtime.BaseAPI {
47
47
  });
48
48
  }
49
49
  /**
50
- * Redirect to a file in Azure Blob Storage. This endpoint is public and it only requires the file key in the URL. The `Content Disposition` header in the response is hardcoded to be `inline` for now, but it can be made a parameter to this endpoint in future if needed. The filename and the content type included in `Content Disposition` are taken from the database record created in `POST /blobs`.\"
51
- * Redirect to a file in Azure Blob Storage
50
+ * Redirect to a file in a cloud file storage. This endpoint is public and it only requires the file key in the URL. The `Content Disposition` header in the response is hardcoded to be `inline` for now, but it can be made a parameter to this endpoint in future if needed. The filename and the content type included in `Content Disposition` are taken from the database record created in `POST /blobs`.\"
51
+ * Redirect to a file in a cloud file storage
52
52
  */
53
53
  blobsIdGet(id, initOverrides) {
54
54
  return __awaiter(this, void 0, void 0, function* () {
@@ -160,15 +160,21 @@ export class HelpersApi extends runtime.BaseAPI {
160
160
  });
161
161
  }
162
162
  /**
163
- * Create a signed upload URL. This endpoint is the first step in creating a file. Just like most ATOM endpoints, this endpoint requires a valid user (that is, an IDP JWT) and some security rights. The security rights are those which might require to attach files to entities like organisations, tenants, and so on. Any of the following security rights grants a permission to create an upload URL * `atom:global:create_tenant` * `atom:global:create_org` * `atom:global:create_tenant_agent` * `atom:tenant:create_org` * `atom:tenant:create_agent` * `atom:org:create_agent` * `atom:tenant:create_tenant_agent` * `vc:tenant:manage` * `vc:org:manage` ATOM generates a random key under which a file will be registered, and creates a record in the database where the key is stored along with the filename and the content type. A client is then expected to use a signed URL present in response field `upload_url` to upload a file to Azure Blob Storage. This URL is only valid for a short period of time specified in response field `upload_url_expires_in_seconds`. Uploading is done via HTTP method `PUT`. Header `x-ms-blob-type: BlockBlob` must be present in this request. The following is an example curl command to upload a file: ``` curl --location --request PUT \\ \'https://meecodevstorage0.blob.core.windows.net/dev/66c35456-eb64-42fb-a31a-806530786fe2?se=2023-01-23T08%3A49%3A29Z&sig=mzuonk01F8L%2F0q7avsMvvenk2NwLFVXYsyWJeu5Jdgc%3D&sp=rw&sr=b&sv=2018-11-09\' \\ --header \'x-ms-blob-type: BlockBlob\' \\ --data-binary \'@/home/john/file.jpg\' ``` After the file is uploaded to Azure Blob Storage, the client is supposed to confirm this upload calling `PUT /blobs/{key}`. The response to `POST /blobs` also contains a URL to retrieve the file, but that functionality is only available after the upload has been confirmed, otherwise it will result in `404 NotFound`. All expired and not confirmed records created with this endpoint will be removed after a while.
163
+ * Create a signed upload URL for one of the supported file storages. This endpoint is the first step in creating a file. Just like most ATOM endpoints, this endpoint requires a valid user (that is, an IDP JWT) and some security rights. The security rights are those which might require to attach files to entities like organisations, tenants, and so on. Any of the following security rights grants a permission to create an upload URL * `atom:global:create_tenant` * `atom:global:create_org` * `atom:global:create_tenant_agent` * `atom:tenant:create_org` * `atom:tenant:create_agent` * `atom:org:create_agent` * `atom:tenant:create_tenant_agent` * `vc:tenant:manage` * `vc:org:manage` ATOM generates a random key under which a file will be registered, and creates a record in the database where the key is stored along with the filename and the content type. A client is then expected to use a signed URL present in response field `upload_url` to upload a file to a cloud file storage. This URL is only valid for a short period of time specified in response field `upload_url_expires_in_seconds`. Uploading is done via HTTP method `PUT`. The response of this endpoint contains a list of headers which much be included in the `PUT` request. The following is an example curl command to upload a file: ``` curl --location --request PUT \\ \'https://meecodevstorage0.blob.core.windows.net/dev/66c35456-eb64-42fb-a31a-806530786fe2?se=2023-01-23T08%3A49%3A29Z&sig=mzuonk01F8L%2F0q7avsMvvenk2NwLFVXYsyWJeu5Jdgc%3D&sp=rw&sr=b&sv=2018-11-09\' \\ --header \'x-ms-blob-type: BlockBlob\' \\ --data-binary \'@/home/john/file.jpg\' ``` After the file is uploaded to Azure Blob Storage, the client is supposed to confirm this upload calling `PUT /blobs/{key}`. The response to `POST /blobs` also contains a URL to retrieve the file, but that functionality is only available after the upload has been confirmed, otherwise it will result in `404 NotFound`. All expired and not confirmed records created with this endpoint will be removed after a while.
164
164
  * Obtain a signed upload URL
165
165
  */
166
166
  blobsPostRaw(requestParameters, initOverrides) {
167
167
  return __awaiter(this, void 0, void 0, function* () {
168
+ if (requestParameters.storageName === null || requestParameters.storageName === undefined) {
169
+ throw new runtime.RequiredError('storageName', 'Required parameter requestParameters.storageName was null or undefined when calling blobsPost.');
170
+ }
168
171
  if (requestParameters.aTOMBlobUploadUrlRequest === null || requestParameters.aTOMBlobUploadUrlRequest === undefined) {
169
172
  throw new runtime.RequiredError('aTOMBlobUploadUrlRequest', 'Required parameter requestParameters.aTOMBlobUploadUrlRequest was null or undefined when calling blobsPost.');
170
173
  }
171
174
  const queryParameters = {};
175
+ if (requestParameters.storageName !== undefined) {
176
+ queryParameters['storage_name'] = requestParameters.storageName;
177
+ }
172
178
  const headerParameters = {};
173
179
  headerParameters['Content-Type'] = 'application/json';
174
180
  if (this.configuration && this.configuration.accessToken) {
@@ -189,12 +195,12 @@ export class HelpersApi extends runtime.BaseAPI {
189
195
  });
190
196
  }
191
197
  /**
192
- * Create a signed upload URL. This endpoint is the first step in creating a file. Just like most ATOM endpoints, this endpoint requires a valid user (that is, an IDP JWT) and some security rights. The security rights are those which might require to attach files to entities like organisations, tenants, and so on. Any of the following security rights grants a permission to create an upload URL * `atom:global:create_tenant` * `atom:global:create_org` * `atom:global:create_tenant_agent` * `atom:tenant:create_org` * `atom:tenant:create_agent` * `atom:org:create_agent` * `atom:tenant:create_tenant_agent` * `vc:tenant:manage` * `vc:org:manage` ATOM generates a random key under which a file will be registered, and creates a record in the database where the key is stored along with the filename and the content type. A client is then expected to use a signed URL present in response field `upload_url` to upload a file to Azure Blob Storage. This URL is only valid for a short period of time specified in response field `upload_url_expires_in_seconds`. Uploading is done via HTTP method `PUT`. Header `x-ms-blob-type: BlockBlob` must be present in this request. The following is an example curl command to upload a file: ``` curl --location --request PUT \\ \'https://meecodevstorage0.blob.core.windows.net/dev/66c35456-eb64-42fb-a31a-806530786fe2?se=2023-01-23T08%3A49%3A29Z&sig=mzuonk01F8L%2F0q7avsMvvenk2NwLFVXYsyWJeu5Jdgc%3D&sp=rw&sr=b&sv=2018-11-09\' \\ --header \'x-ms-blob-type: BlockBlob\' \\ --data-binary \'@/home/john/file.jpg\' ``` After the file is uploaded to Azure Blob Storage, the client is supposed to confirm this upload calling `PUT /blobs/{key}`. The response to `POST /blobs` also contains a URL to retrieve the file, but that functionality is only available after the upload has been confirmed, otherwise it will result in `404 NotFound`. All expired and not confirmed records created with this endpoint will be removed after a while.
198
+ * Create a signed upload URL for one of the supported file storages. This endpoint is the first step in creating a file. Just like most ATOM endpoints, this endpoint requires a valid user (that is, an IDP JWT) and some security rights. The security rights are those which might require to attach files to entities like organisations, tenants, and so on. Any of the following security rights grants a permission to create an upload URL * `atom:global:create_tenant` * `atom:global:create_org` * `atom:global:create_tenant_agent` * `atom:tenant:create_org` * `atom:tenant:create_agent` * `atom:org:create_agent` * `atom:tenant:create_tenant_agent` * `vc:tenant:manage` * `vc:org:manage` ATOM generates a random key under which a file will be registered, and creates a record in the database where the key is stored along with the filename and the content type. A client is then expected to use a signed URL present in response field `upload_url` to upload a file to a cloud file storage. This URL is only valid for a short period of time specified in response field `upload_url_expires_in_seconds`. Uploading is done via HTTP method `PUT`. The response of this endpoint contains a list of headers which much be included in the `PUT` request. The following is an example curl command to upload a file: ``` curl --location --request PUT \\ \'https://meecodevstorage0.blob.core.windows.net/dev/66c35456-eb64-42fb-a31a-806530786fe2?se=2023-01-23T08%3A49%3A29Z&sig=mzuonk01F8L%2F0q7avsMvvenk2NwLFVXYsyWJeu5Jdgc%3D&sp=rw&sr=b&sv=2018-11-09\' \\ --header \'x-ms-blob-type: BlockBlob\' \\ --data-binary \'@/home/john/file.jpg\' ``` After the file is uploaded to Azure Blob Storage, the client is supposed to confirm this upload calling `PUT /blobs/{key}`. The response to `POST /blobs` also contains a URL to retrieve the file, but that functionality is only available after the upload has been confirmed, otherwise it will result in `404 NotFound`. All expired and not confirmed records created with this endpoint will be removed after a while.
193
199
  * Obtain a signed upload URL
194
200
  */
195
- blobsPost(aTOMBlobUploadUrlRequest, initOverrides) {
201
+ blobsPost(storageName, aTOMBlobUploadUrlRequest, initOverrides) {
196
202
  return __awaiter(this, void 0, void 0, function* () {
197
- const response = yield this.blobsPostRaw({ aTOMBlobUploadUrlRequest: aTOMBlobUploadUrlRequest }, initOverrides);
203
+ const response = yield this.blobsPostRaw({ storageName: storageName, aTOMBlobUploadUrlRequest: aTOMBlobUploadUrlRequest }, initOverrides);
198
204
  return yield response.value();
199
205
  });
200
206
  }
@@ -808,10 +808,10 @@ export class ItemsApi extends runtime.BaseAPI {
808
808
  * Delete an item. If the item is an item shared with the current user, the corresponding share is deleted together with the item.
809
809
  * Delete an item
810
810
  */
811
- itemsIdDeleteRaw(requestParameters, initOverrides) {
811
+ itemsItemIdDeleteRaw(requestParameters, initOverrides) {
812
812
  return __awaiter(this, void 0, void 0, function* () {
813
- if (requestParameters.id === null || requestParameters.id === undefined) {
814
- throw new runtime.RequiredError('id', 'Required parameter requestParameters.id was null or undefined when calling itemsIdDelete.');
813
+ if (requestParameters.itemId === null || requestParameters.itemId === undefined) {
814
+ throw new runtime.RequiredError('itemId', 'Required parameter requestParameters.itemId was null or undefined when calling itemsItemIdDelete.');
815
815
  }
816
816
  const queryParameters = {};
817
817
  const headerParameters = {};
@@ -829,7 +829,7 @@ export class ItemsApi extends runtime.BaseAPI {
829
829
  }
830
830
  }
831
831
  const response = yield this.request({
832
- path: `/items/{id}`.replace(`{${"id"}}`, encodeURIComponent(String(requestParameters.id))),
832
+ path: `/items/{item_id}`.replace(`{${"item_id"}}`, encodeURIComponent(String(requestParameters.itemId))),
833
833
  method: 'DELETE',
834
834
  headers: headerParameters,
835
835
  query: queryParameters,
@@ -841,19 +841,19 @@ export class ItemsApi extends runtime.BaseAPI {
841
841
  * Delete an item. If the item is an item shared with the current user, the corresponding share is deleted together with the item.
842
842
  * Delete an item
843
843
  */
844
- itemsIdDelete(id, meecoDelegationId, meecoOrganisationId, initOverrides) {
844
+ itemsItemIdDelete(itemId, meecoDelegationId, meecoOrganisationId, initOverrides) {
845
845
  return __awaiter(this, void 0, void 0, function* () {
846
- yield this.itemsIdDeleteRaw({ id: id, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
846
+ yield this.itemsItemIdDeleteRaw({ itemId: itemId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
847
847
  });
848
848
  }
849
849
  /**
850
- * Retrieve a specific Item by `id`.
851
- * Get Item
850
+ * Retrieve a specific Item by `item_id`.
851
+ * Get item
852
852
  */
853
- itemsIdGetRaw(requestParameters, initOverrides) {
853
+ itemsItemIdGetRaw(requestParameters, initOverrides) {
854
854
  return __awaiter(this, void 0, void 0, function* () {
855
- if (requestParameters.id === null || requestParameters.id === undefined) {
856
- throw new runtime.RequiredError('id', 'Required parameter requestParameters.id was null or undefined when calling itemsIdGet.');
855
+ if (requestParameters.itemId === null || requestParameters.itemId === undefined) {
856
+ throw new runtime.RequiredError('itemId', 'Required parameter requestParameters.itemId was null or undefined when calling itemsItemIdGet.');
857
857
  }
858
858
  const queryParameters = {};
859
859
  const headerParameters = {};
@@ -871,7 +871,7 @@ export class ItemsApi extends runtime.BaseAPI {
871
871
  }
872
872
  }
873
873
  const response = yield this.request({
874
- path: `/items/{id}`.replace(`{${"id"}}`, encodeURIComponent(String(requestParameters.id))),
874
+ path: `/items/{item_id}`.replace(`{${"item_id"}}`, encodeURIComponent(String(requestParameters.itemId))),
875
875
  method: 'GET',
876
876
  headers: headerParameters,
877
877
  query: queryParameters,
@@ -880,23 +880,23 @@ export class ItemsApi extends runtime.BaseAPI {
880
880
  });
881
881
  }
882
882
  /**
883
- * Retrieve a specific Item by `id`.
884
- * Get Item
883
+ * Retrieve a specific Item by `item_id`.
884
+ * Get item
885
885
  */
886
- itemsIdGet(id, meecoDelegationId, meecoOrganisationId, initOverrides) {
886
+ itemsItemIdGet(itemId, meecoDelegationId, meecoOrganisationId, initOverrides) {
887
887
  return __awaiter(this, void 0, void 0, function* () {
888
- const response = yield this.itemsIdGetRaw({ id: id, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
888
+ const response = yield this.itemsItemIdGetRaw({ itemId: itemId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
889
889
  return yield response.value();
890
890
  });
891
891
  }
892
892
  /**
893
- * Update an Item specified by `id` with fields provided in the JSON body. --- ### Classifications In this endpoint it is possible to link the item and its slots to classification nodes, unlink the item and its slots from classification nodes, and to create classification nodes in user-owned classification schemes if they do not exist yet. There are 2 types of classification schemes: * owned by users - each user can create their own classification nodes * global - nodes are created by the system There are 5 parameters for classification of slots and items in `POST /items`: * `node_id` * `node_name` * `scheme_id` * `scheme_name` * `_destroy` Both a classification scheme and a classification node can be referred to by their name or their ID. If `id` is used, `scheme_id` and `scheme` may be omitted. Flag `_destroy` is used to unlink a classification node from a slot or the item. Example payload classifications: ``` classification_nodes_attributes: [ {id: \"c1b1d2b3-a887-4cc2-86e8-285268df598a\"}, {scheme: \"region\", id: \"315e4e30-93f0-4232-b977-b51f90b18288\"}, {scheme: \"region\", name: \"france\", \"_destroy\": true}, {scheme_id: \"34c8c951-aa25-4d9a-9a9a-dbb5f43b821b\", name: \"netherlands\"}, {scheme_id: \"34c8c951-aa25-4d9a-9a9a-dbb5f43b821b\", id: \"16557bff-21fe-4bb1-8b0a-0a7847dfc7d6\"}, {scheme: \"tag\", name: \"my-own-cool-tag\"} ] ``` If node `france` is missing in scheme region, the service will return an error, because scheme `region` is a global scheme. `(owned_by_user=false)`. If node `my-own-cool-tag` is missing in scheme `tag`, it will be created, because scheme `tag` is a user owned scheme. ---
893
+ * Update an item specified by `item_id` with fields provided in the JSON body. --- ### Classifications In this endpoint it is possible to link the item and its slots to classification nodes, unlink the item and its slots from classification nodes, and to create classification nodes in user-owned classification schemes if they do not exist yet. There are 2 types of classification schemes: * owned by users - each user can create their own classification nodes * global - nodes are created by the system There are 5 parameters for classification of slots and items in `POST /items`: * `node_id` * `node_name` * `scheme_id` * `scheme_name` * `_destroy` Both a classification scheme and a classification node can be referred to by their name or their ID. If `id` is used, `scheme_id` and `scheme` may be omitted. Flag `_destroy` is used to unlink a classification node from a slot or the item. Example payload classifications: ``` classification_nodes_attributes: [ {id: \"c1b1d2b3-a887-4cc2-86e8-285268df598a\"}, {scheme: \"region\", id: \"315e4e30-93f0-4232-b977-b51f90b18288\"}, {scheme: \"region\", name: \"france\", \"_destroy\": true}, {scheme_id: \"34c8c951-aa25-4d9a-9a9a-dbb5f43b821b\", name: \"netherlands\"}, {scheme_id: \"34c8c951-aa25-4d9a-9a9a-dbb5f43b821b\", id: \"16557bff-21fe-4bb1-8b0a-0a7847dfc7d6\"}, {scheme: \"tag\", name: \"my-own-cool-tag\"} ] ``` If node `france` is missing in scheme region, the service will return an error, because scheme `region` is a global scheme. `(owned_by_user=false)`. If node `my-own-cool-tag` is missing in scheme `tag`, it will be created, because scheme `tag` is a user owned scheme. ---
894
894
  * Update an item
895
895
  */
896
- itemsIdPutRaw(requestParameters, initOverrides) {
896
+ itemsItemIdPutRaw(requestParameters, initOverrides) {
897
897
  return __awaiter(this, void 0, void 0, function* () {
898
- if (requestParameters.id === null || requestParameters.id === undefined) {
899
- throw new runtime.RequiredError('id', 'Required parameter requestParameters.id was null or undefined when calling itemsIdPut.');
898
+ if (requestParameters.itemId === null || requestParameters.itemId === undefined) {
899
+ throw new runtime.RequiredError('itemId', 'Required parameter requestParameters.itemId was null or undefined when calling itemsItemIdPut.');
900
900
  }
901
901
  const queryParameters = {};
902
902
  const headerParameters = {};
@@ -915,7 +915,7 @@ export class ItemsApi extends runtime.BaseAPI {
915
915
  }
916
916
  }
917
917
  const response = yield this.request({
918
- path: `/items/{id}`.replace(`{${"id"}}`, encodeURIComponent(String(requestParameters.id))),
918
+ path: `/items/{item_id}`.replace(`{${"item_id"}}`, encodeURIComponent(String(requestParameters.itemId))),
919
919
  method: 'PUT',
920
920
  headers: headerParameters,
921
921
  query: queryParameters,
@@ -925,12 +925,12 @@ export class ItemsApi extends runtime.BaseAPI {
925
925
  });
926
926
  }
927
927
  /**
928
- * Update an Item specified by `id` with fields provided in the JSON body. --- ### Classifications In this endpoint it is possible to link the item and its slots to classification nodes, unlink the item and its slots from classification nodes, and to create classification nodes in user-owned classification schemes if they do not exist yet. There are 2 types of classification schemes: * owned by users - each user can create their own classification nodes * global - nodes are created by the system There are 5 parameters for classification of slots and items in `POST /items`: * `node_id` * `node_name` * `scheme_id` * `scheme_name` * `_destroy` Both a classification scheme and a classification node can be referred to by their name or their ID. If `id` is used, `scheme_id` and `scheme` may be omitted. Flag `_destroy` is used to unlink a classification node from a slot or the item. Example payload classifications: ``` classification_nodes_attributes: [ {id: \"c1b1d2b3-a887-4cc2-86e8-285268df598a\"}, {scheme: \"region\", id: \"315e4e30-93f0-4232-b977-b51f90b18288\"}, {scheme: \"region\", name: \"france\", \"_destroy\": true}, {scheme_id: \"34c8c951-aa25-4d9a-9a9a-dbb5f43b821b\", name: \"netherlands\"}, {scheme_id: \"34c8c951-aa25-4d9a-9a9a-dbb5f43b821b\", id: \"16557bff-21fe-4bb1-8b0a-0a7847dfc7d6\"}, {scheme: \"tag\", name: \"my-own-cool-tag\"} ] ``` If node `france` is missing in scheme region, the service will return an error, because scheme `region` is a global scheme. `(owned_by_user=false)`. If node `my-own-cool-tag` is missing in scheme `tag`, it will be created, because scheme `tag` is a user owned scheme. ---
928
+ * Update an item specified by `item_id` with fields provided in the JSON body. --- ### Classifications In this endpoint it is possible to link the item and its slots to classification nodes, unlink the item and its slots from classification nodes, and to create classification nodes in user-owned classification schemes if they do not exist yet. There are 2 types of classification schemes: * owned by users - each user can create their own classification nodes * global - nodes are created by the system There are 5 parameters for classification of slots and items in `POST /items`: * `node_id` * `node_name` * `scheme_id` * `scheme_name` * `_destroy` Both a classification scheme and a classification node can be referred to by their name or their ID. If `id` is used, `scheme_id` and `scheme` may be omitted. Flag `_destroy` is used to unlink a classification node from a slot or the item. Example payload classifications: ``` classification_nodes_attributes: [ {id: \"c1b1d2b3-a887-4cc2-86e8-285268df598a\"}, {scheme: \"region\", id: \"315e4e30-93f0-4232-b977-b51f90b18288\"}, {scheme: \"region\", name: \"france\", \"_destroy\": true}, {scheme_id: \"34c8c951-aa25-4d9a-9a9a-dbb5f43b821b\", name: \"netherlands\"}, {scheme_id: \"34c8c951-aa25-4d9a-9a9a-dbb5f43b821b\", id: \"16557bff-21fe-4bb1-8b0a-0a7847dfc7d6\"}, {scheme: \"tag\", name: \"my-own-cool-tag\"} ] ``` If node `france` is missing in scheme region, the service will return an error, because scheme `region` is a global scheme. `(owned_by_user=false)`. If node `my-own-cool-tag` is missing in scheme `tag`, it will be created, because scheme `tag` is a user owned scheme. ---
929
929
  * Update an item
930
930
  */
931
- itemsIdPut(id, meecoDelegationId, meecoOrganisationId, putItemsRequest, initOverrides) {
931
+ itemsItemIdPut(itemId, meecoDelegationId, meecoOrganisationId, putItemsRequest, initOverrides) {
932
932
  return __awaiter(this, void 0, void 0, function* () {
933
- const response = yield this.itemsIdPutRaw({ id: id, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId, putItemsRequest: putItemsRequest }, initOverrides);
933
+ const response = yield this.itemsItemIdPutRaw({ itemId: itemId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId, putItemsRequest: putItemsRequest }, initOverrides);
934
934
  return yield response.value();
935
935
  });
936
936
  }