@meeco/svx-api-sdk 1.0.0-stage.20240430145443.1d5661a → 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
@@ -280,16 +280,17 @@ class ConnectionsApi extends runtime.BaseAPI {
280
280
  });
281
281
  }
282
282
  /**
283
- * Delete an invitation by its token or ID. Only the user who created the invitation may delete it.
284
- * Delete an invitation
283
+ * 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
284
+ * Accept an invitation
285
285
  */
286
- invitationsIdDeleteRaw(requestParameters, initOverrides) {
286
+ invitationsInvitationIdAcceptPostRaw(requestParameters, initOverrides) {
287
287
  return __awaiter(this, void 0, void 0, function* () {
288
- if (requestParameters.id === null || requestParameters.id === undefined) {
289
- throw new runtime.RequiredError('id', 'Required parameter requestParameters.id was null or undefined when calling invitationsIdDelete.');
288
+ if (requestParameters.invitationId === null || requestParameters.invitationId === undefined) {
289
+ throw new runtime.RequiredError('invitationId', 'Required parameter requestParameters.invitationId was null or undefined when calling invitationsInvitationIdAcceptPost.');
290
290
  }
291
291
  const queryParameters = {};
292
292
  const headerParameters = {};
293
+ headerParameters['Content-Type'] = 'application/json';
293
294
  if (requestParameters.meecoDelegationId !== undefined && requestParameters.meecoDelegationId !== null) {
294
295
  headerParameters['Meeco-Delegation-Id'] = String(requestParameters.meecoDelegationId);
295
296
  }
@@ -304,31 +305,33 @@ class ConnectionsApi extends runtime.BaseAPI {
304
305
  }
305
306
  }
306
307
  const response = yield this.request({
307
- path: `/invitations/{id}`.replace(`{${"id"}}`, encodeURIComponent(String(requestParameters.id))),
308
- method: 'DELETE',
308
+ path: `/invitations/{invitation_id}/accept`.replace(`{${"invitation_id"}}`, encodeURIComponent(String(requestParameters.invitationId))),
309
+ method: 'POST',
309
310
  headers: headerParameters,
310
311
  query: queryParameters,
312
+ body: (0, models_1.AcceptInvitationsRequestToJSON)(requestParameters.acceptInvitationsRequest),
311
313
  }, initOverrides);
312
- return new runtime.VoidApiResponse(response);
314
+ return new runtime.JSONApiResponse(response, (jsonValue) => (0, models_1.VaultInvitationAcceptedResponseFromJSON)(jsonValue));
313
315
  });
314
316
  }
315
317
  /**
316
- * Delete an invitation by its token or ID. Only the user who created the invitation may delete it.
317
- * Delete an invitation
318
+ * 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
319
+ * Accept an invitation
318
320
  */
319
- invitationsIdDelete(id, meecoDelegationId, meecoOrganisationId, initOverrides) {
321
+ invitationsInvitationIdAcceptPost(invitationId, meecoDelegationId, meecoOrganisationId, acceptInvitationsRequest, initOverrides) {
320
322
  return __awaiter(this, void 0, void 0, function* () {
321
- yield this.invitationsIdDeleteRaw({ id: id, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
323
+ const response = yield this.invitationsInvitationIdAcceptPostRaw({ invitationId: invitationId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId, acceptInvitationsRequest: acceptInvitationsRequest }, initOverrides);
324
+ return yield response.value();
322
325
  });
323
326
  }
324
327
  /**
325
- * 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
326
- * Read an invitation
328
+ * 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.
329
+ * Reject an accepted invitation
327
330
  */
328
- invitationsIdGetRaw(requestParameters, initOverrides) {
331
+ invitationsInvitationIdCancelDeleteRaw(requestParameters, initOverrides) {
329
332
  return __awaiter(this, void 0, void 0, function* () {
330
- if (requestParameters.id === null || requestParameters.id === undefined) {
331
- throw new runtime.RequiredError('id', 'Required parameter requestParameters.id was null or undefined when calling invitationsIdGet.');
333
+ if (requestParameters.invitationId === null || requestParameters.invitationId === undefined) {
334
+ throw new runtime.RequiredError('invitationId', 'Required parameter requestParameters.invitationId was null or undefined when calling invitationsInvitationIdCancelDelete.');
332
335
  }
333
336
  const queryParameters = {};
334
337
  const headerParameters = {};
@@ -346,35 +349,36 @@ class ConnectionsApi extends runtime.BaseAPI {
346
349
  }
347
350
  }
348
351
  const response = yield this.request({
349
- path: `/invitations/{id}`.replace(`{${"id"}}`, encodeURIComponent(String(requestParameters.id))),
350
- method: 'GET',
352
+ path: `/invitations/{invitation_id}/cancel`.replace(`{${"invitation_id"}}`, encodeURIComponent(String(requestParameters.invitationId))),
353
+ method: 'DELETE',
351
354
  headers: headerParameters,
352
355
  query: queryParameters,
353
356
  }, initOverrides);
354
- return new runtime.JSONApiResponse(response, (jsonValue) => (0, models_1.InvitationWithShareIntentsResponseFromJSON)(jsonValue));
357
+ return new runtime.JSONApiResponse(response, (jsonValue) => (0, models_1.InvitationResponseFromJSON)(jsonValue));
355
358
  });
356
359
  }
357
360
  /**
358
- * 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
359
- * Read an invitation
361
+ * 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.
362
+ * Reject an accepted invitation
360
363
  */
361
- invitationsIdGet(id, meecoDelegationId, meecoOrganisationId, initOverrides) {
364
+ invitationsInvitationIdCancelDelete(invitationId, meecoDelegationId, meecoOrganisationId, initOverrides) {
362
365
  return __awaiter(this, void 0, void 0, function* () {
363
- const response = yield this.invitationsIdGetRaw({ id: id, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
366
+ const response = yield this.invitationsInvitationIdCancelDeleteRaw({ invitationId: invitationId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
364
367
  return yield response.value();
365
368
  });
366
369
  }
367
370
  /**
368
- * 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.
369
- * Reject an accepted invitation
371
+ * 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
372
+ * Confirm an accepted invitation
370
373
  */
371
- invitationsInvitationIdCancelDeleteRaw(requestParameters, initOverrides) {
374
+ invitationsInvitationIdConfirmPostRaw(requestParameters, initOverrides) {
372
375
  return __awaiter(this, void 0, void 0, function* () {
373
376
  if (requestParameters.invitationId === null || requestParameters.invitationId === undefined) {
374
- throw new runtime.RequiredError('invitationId', 'Required parameter requestParameters.invitationId was null or undefined when calling invitationsInvitationIdCancelDelete.');
377
+ throw new runtime.RequiredError('invitationId', 'Required parameter requestParameters.invitationId was null or undefined when calling invitationsInvitationIdConfirmPost.');
375
378
  }
376
379
  const queryParameters = {};
377
380
  const headerParameters = {};
381
+ headerParameters['Content-Type'] = 'application/json';
378
382
  if (requestParameters.meecoDelegationId !== undefined && requestParameters.meecoDelegationId !== null) {
379
383
  headerParameters['Meeco-Delegation-Id'] = String(requestParameters.meecoDelegationId);
380
384
  }
@@ -389,36 +393,36 @@ class ConnectionsApi extends runtime.BaseAPI {
389
393
  }
390
394
  }
391
395
  const response = yield this.request({
392
- path: `/invitations/{invitation_id}/cancel`.replace(`{${"invitation_id"}}`, encodeURIComponent(String(requestParameters.invitationId))),
393
- method: 'DELETE',
396
+ path: `/invitations/{invitation_id}/confirm`.replace(`{${"invitation_id"}}`, encodeURIComponent(String(requestParameters.invitationId))),
397
+ method: 'POST',
394
398
  headers: headerParameters,
395
399
  query: queryParameters,
400
+ body: (0, models_1.AcceptInvitationsRequest1ToJSON)(requestParameters.acceptInvitationsRequest1),
396
401
  }, initOverrides);
397
- return new runtime.JSONApiResponse(response, (jsonValue) => (0, models_1.InvitationResponseFromJSON)(jsonValue));
402
+ return new runtime.JSONApiResponse(response, (jsonValue) => (0, models_1.VaultInvitationAcceptedResponseFromJSON)(jsonValue));
398
403
  });
399
404
  }
400
405
  /**
401
- * 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.
402
- * Reject an accepted invitation
406
+ * 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
407
+ * Confirm an accepted invitation
403
408
  */
404
- invitationsInvitationIdCancelDelete(invitationId, meecoDelegationId, meecoOrganisationId, initOverrides) {
409
+ invitationsInvitationIdConfirmPost(invitationId, meecoDelegationId, meecoOrganisationId, acceptInvitationsRequest1, initOverrides) {
405
410
  return __awaiter(this, void 0, void 0, function* () {
406
- const response = yield this.invitationsInvitationIdCancelDeleteRaw({ invitationId: invitationId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
411
+ const response = yield this.invitationsInvitationIdConfirmPostRaw({ invitationId: invitationId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId, acceptInvitationsRequest1: acceptInvitationsRequest1 }, initOverrides);
407
412
  return yield response.value();
408
413
  });
409
414
  }
410
415
  /**
411
- * 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
412
- * Confirm an accepted invitation
416
+ * Delete an invitation by its token or ID. Only the user who created the invitation may delete it.
417
+ * Delete an invitation
413
418
  */
414
- invitationsInvitationIdConfirmPostRaw(requestParameters, initOverrides) {
419
+ invitationsInvitationIdDeleteRaw(requestParameters, initOverrides) {
415
420
  return __awaiter(this, void 0, void 0, function* () {
416
421
  if (requestParameters.invitationId === null || requestParameters.invitationId === undefined) {
417
- throw new runtime.RequiredError('invitationId', 'Required parameter requestParameters.invitationId was null or undefined when calling invitationsInvitationIdConfirmPost.');
422
+ throw new runtime.RequiredError('invitationId', 'Required parameter requestParameters.invitationId was null or undefined when calling invitationsInvitationIdDelete.');
418
423
  }
419
424
  const queryParameters = {};
420
425
  const headerParameters = {};
421
- headerParameters['Content-Type'] = 'application/json';
422
426
  if (requestParameters.meecoDelegationId !== undefined && requestParameters.meecoDelegationId !== null) {
423
427
  headerParameters['Meeco-Delegation-Id'] = String(requestParameters.meecoDelegationId);
424
428
  }
@@ -433,37 +437,34 @@ class ConnectionsApi extends runtime.BaseAPI {
433
437
  }
434
438
  }
435
439
  const response = yield this.request({
436
- path: `/invitations/{invitation_id}/confirm`.replace(`{${"invitation_id"}}`, encodeURIComponent(String(requestParameters.invitationId))),
437
- method: 'POST',
440
+ path: `/invitations/{invitation_id}`.replace(`{${"invitation_id"}}`, encodeURIComponent(String(requestParameters.invitationId))),
441
+ method: 'DELETE',
438
442
  headers: headerParameters,
439
443
  query: queryParameters,
440
- body: (0, models_1.AcceptInvitationsRequest1ToJSON)(requestParameters.acceptInvitationsRequest1),
441
444
  }, initOverrides);
442
- return new runtime.JSONApiResponse(response, (jsonValue) => (0, models_1.VaultInvitationAcceptedResponseFromJSON)(jsonValue));
445
+ return new runtime.VoidApiResponse(response);
443
446
  });
444
447
  }
445
448
  /**
446
- * 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
447
- * Confirm an accepted invitation
449
+ * Delete an invitation by its token or ID. Only the user who created the invitation may delete it.
450
+ * Delete an invitation
448
451
  */
449
- invitationsInvitationIdConfirmPost(invitationId, meecoDelegationId, meecoOrganisationId, acceptInvitationsRequest1, initOverrides) {
452
+ invitationsInvitationIdDelete(invitationId, meecoDelegationId, meecoOrganisationId, initOverrides) {
450
453
  return __awaiter(this, void 0, void 0, function* () {
451
- const response = yield this.invitationsInvitationIdConfirmPostRaw({ invitationId: invitationId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId, acceptInvitationsRequest1: acceptInvitationsRequest1 }, initOverrides);
452
- return yield response.value();
454
+ yield this.invitationsInvitationIdDeleteRaw({ invitationId: invitationId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
453
455
  });
454
456
  }
455
457
  /**
456
- * 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
457
- * Accept an invitation
458
+ * 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
459
+ * Read an invitation
458
460
  */
459
- invitationsInvitationTokenAcceptPostRaw(requestParameters, initOverrides) {
461
+ invitationsInvitationIdGetRaw(requestParameters, initOverrides) {
460
462
  return __awaiter(this, void 0, void 0, function* () {
461
- if (requestParameters.invitationToken === null || requestParameters.invitationToken === undefined) {
462
- throw new runtime.RequiredError('invitationToken', 'Required parameter requestParameters.invitationToken was null or undefined when calling invitationsInvitationTokenAcceptPost.');
463
+ if (requestParameters.invitationId === null || requestParameters.invitationId === undefined) {
464
+ throw new runtime.RequiredError('invitationId', 'Required parameter requestParameters.invitationId was null or undefined when calling invitationsInvitationIdGet.');
463
465
  }
464
466
  const queryParameters = {};
465
467
  const headerParameters = {};
466
- headerParameters['Content-Type'] = 'application/json';
467
468
  if (requestParameters.meecoDelegationId !== undefined && requestParameters.meecoDelegationId !== null) {
468
469
  headerParameters['Meeco-Delegation-Id'] = String(requestParameters.meecoDelegationId);
469
470
  }
@@ -478,22 +479,21 @@ class ConnectionsApi extends runtime.BaseAPI {
478
479
  }
479
480
  }
480
481
  const response = yield this.request({
481
- path: `/invitations/{invitation_token}/accept`.replace(`{${"invitation_token"}}`, encodeURIComponent(String(requestParameters.invitationToken))),
482
- method: 'POST',
482
+ path: `/invitations/{invitation_id}`.replace(`{${"invitation_id"}}`, encodeURIComponent(String(requestParameters.invitationId))),
483
+ method: 'GET',
483
484
  headers: headerParameters,
484
485
  query: queryParameters,
485
- body: (0, models_1.AcceptInvitationsRequestToJSON)(requestParameters.acceptInvitationsRequest),
486
486
  }, initOverrides);
487
- return new runtime.JSONApiResponse(response, (jsonValue) => (0, models_1.VaultInvitationAcceptedResponseFromJSON)(jsonValue));
487
+ return new runtime.JSONApiResponse(response, (jsonValue) => (0, models_1.InvitationWithShareIntentsResponseFromJSON)(jsonValue));
488
488
  });
489
489
  }
490
490
  /**
491
- * 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
492
- * Accept an invitation
491
+ * 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
492
+ * Read an invitation
493
493
  */
494
- invitationsInvitationTokenAcceptPost(invitationToken, meecoDelegationId, meecoOrganisationId, acceptInvitationsRequest, initOverrides) {
494
+ invitationsInvitationIdGet(invitationId, meecoDelegationId, meecoOrganisationId, initOverrides) {
495
495
  return __awaiter(this, void 0, void 0, function* () {
496
- const response = yield this.invitationsInvitationTokenAcceptPostRaw({ invitationToken: invitationToken, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId, acceptInvitationsRequest: acceptInvitationsRequest }, initOverrides);
496
+ const response = yield this.invitationsInvitationIdGetRaw({ invitationId: invitationId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
497
497
  return yield response.value();
498
498
  });
499
499
  }
@@ -501,10 +501,10 @@ class ConnectionsApi extends runtime.BaseAPI {
501
501
  * Reject an invitation. This endpoint is only available if the multistep invitation flow is enabled.
502
502
  * Reject an invitation
503
503
  */
504
- invitationsInvitationTokenRejectDeleteRaw(requestParameters, initOverrides) {
504
+ invitationsInvitationIdRejectDeleteRaw(requestParameters, initOverrides) {
505
505
  return __awaiter(this, void 0, void 0, function* () {
506
- if (requestParameters.invitationToken === null || requestParameters.invitationToken === undefined) {
507
- throw new runtime.RequiredError('invitationToken', 'Required parameter requestParameters.invitationToken was null or undefined when calling invitationsInvitationTokenRejectDelete.');
506
+ if (requestParameters.invitationId === null || requestParameters.invitationId === undefined) {
507
+ throw new runtime.RequiredError('invitationId', 'Required parameter requestParameters.invitationId was null or undefined when calling invitationsInvitationIdRejectDelete.');
508
508
  }
509
509
  const queryParameters = {};
510
510
  const headerParameters = {};
@@ -522,7 +522,7 @@ class ConnectionsApi extends runtime.BaseAPI {
522
522
  }
523
523
  }
524
524
  const response = yield this.request({
525
- path: `/invitations/{invitation_token}/reject`.replace(`{${"invitation_token"}}`, encodeURIComponent(String(requestParameters.invitationToken))),
525
+ path: `/invitations/{invitation_id}/reject`.replace(`{${"invitation_id"}}`, encodeURIComponent(String(requestParameters.invitationId))),
526
526
  method: 'DELETE',
527
527
  headers: headerParameters,
528
528
  query: queryParameters,
@@ -534,9 +534,9 @@ class ConnectionsApi extends runtime.BaseAPI {
534
534
  * Reject an invitation. This endpoint is only available if the multistep invitation flow is enabled.
535
535
  * Reject an invitation
536
536
  */
537
- invitationsInvitationTokenRejectDelete(invitationToken, meecoDelegationId, meecoOrganisationId, initOverrides) {
537
+ invitationsInvitationIdRejectDelete(invitationId, meecoDelegationId, meecoOrganisationId, initOverrides) {
538
538
  return __awaiter(this, void 0, void 0, function* () {
539
- const response = yield this.invitationsInvitationTokenRejectDeleteRaw({ invitationToken: invitationToken, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
539
+ const response = yield this.invitationsInvitationIdRejectDeleteRaw({ invitationId: invitationId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
540
540
  return yield response.value();
541
541
  });
542
542
  }
@@ -53,8 +53,8 @@ const models_1 = require("../models");
53
53
  */
54
54
  class HelpersApi extends runtime.BaseAPI {
55
55
  /**
56
- * 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`.\"
57
- * Redirect to a file in Azure Blob Storage
56
+ * 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`.\"
57
+ * Redirect to a file in a cloud file storage
58
58
  */
59
59
  blobsIdGetRaw(requestParameters, initOverrides) {
60
60
  return __awaiter(this, void 0, void 0, function* () {
@@ -73,8 +73,8 @@ class HelpersApi extends runtime.BaseAPI {
73
73
  });
74
74
  }
75
75
  /**
76
- * 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`.\"
77
- * Redirect to a file in Azure Blob Storage
76
+ * 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`.\"
77
+ * Redirect to a file in a cloud file storage
78
78
  */
79
79
  blobsIdGet(id, initOverrides) {
80
80
  return __awaiter(this, void 0, void 0, function* () {
@@ -186,15 +186,21 @@ class HelpersApi extends runtime.BaseAPI {
186
186
  });
187
187
  }
188
188
  /**
189
- * 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.
189
+ * 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.
190
190
  * Obtain a signed upload URL
191
191
  */
192
192
  blobsPostRaw(requestParameters, initOverrides) {
193
193
  return __awaiter(this, void 0, void 0, function* () {
194
+ if (requestParameters.storageName === null || requestParameters.storageName === undefined) {
195
+ throw new runtime.RequiredError('storageName', 'Required parameter requestParameters.storageName was null or undefined when calling blobsPost.');
196
+ }
194
197
  if (requestParameters.aTOMBlobUploadUrlRequest === null || requestParameters.aTOMBlobUploadUrlRequest === undefined) {
195
198
  throw new runtime.RequiredError('aTOMBlobUploadUrlRequest', 'Required parameter requestParameters.aTOMBlobUploadUrlRequest was null or undefined when calling blobsPost.');
196
199
  }
197
200
  const queryParameters = {};
201
+ if (requestParameters.storageName !== undefined) {
202
+ queryParameters['storage_name'] = requestParameters.storageName;
203
+ }
198
204
  const headerParameters = {};
199
205
  headerParameters['Content-Type'] = 'application/json';
200
206
  if (this.configuration && this.configuration.accessToken) {
@@ -215,12 +221,12 @@ class HelpersApi extends runtime.BaseAPI {
215
221
  });
216
222
  }
217
223
  /**
218
- * 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.
224
+ * 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.
219
225
  * Obtain a signed upload URL
220
226
  */
221
- blobsPost(aTOMBlobUploadUrlRequest, initOverrides) {
227
+ blobsPost(storageName, aTOMBlobUploadUrlRequest, initOverrides) {
222
228
  return __awaiter(this, void 0, void 0, function* () {
223
- const response = yield this.blobsPostRaw({ aTOMBlobUploadUrlRequest: aTOMBlobUploadUrlRequest }, initOverrides);
229
+ const response = yield this.blobsPostRaw({ storageName: storageName, aTOMBlobUploadUrlRequest: aTOMBlobUploadUrlRequest }, initOverrides);
224
230
  return yield response.value();
225
231
  });
226
232
  }
@@ -834,10 +834,10 @@ class ItemsApi extends runtime.BaseAPI {
834
834
  * Delete an item. If the item is an item shared with the current user, the corresponding share is deleted together with the item.
835
835
  * Delete an item
836
836
  */
837
- itemsIdDeleteRaw(requestParameters, initOverrides) {
837
+ itemsItemIdDeleteRaw(requestParameters, initOverrides) {
838
838
  return __awaiter(this, void 0, void 0, function* () {
839
- if (requestParameters.id === null || requestParameters.id === undefined) {
840
- throw new runtime.RequiredError('id', 'Required parameter requestParameters.id was null or undefined when calling itemsIdDelete.');
839
+ if (requestParameters.itemId === null || requestParameters.itemId === undefined) {
840
+ throw new runtime.RequiredError('itemId', 'Required parameter requestParameters.itemId was null or undefined when calling itemsItemIdDelete.');
841
841
  }
842
842
  const queryParameters = {};
843
843
  const headerParameters = {};
@@ -855,7 +855,7 @@ class ItemsApi extends runtime.BaseAPI {
855
855
  }
856
856
  }
857
857
  const response = yield this.request({
858
- path: `/items/{id}`.replace(`{${"id"}}`, encodeURIComponent(String(requestParameters.id))),
858
+ path: `/items/{item_id}`.replace(`{${"item_id"}}`, encodeURIComponent(String(requestParameters.itemId))),
859
859
  method: 'DELETE',
860
860
  headers: headerParameters,
861
861
  query: queryParameters,
@@ -867,19 +867,19 @@ class ItemsApi extends runtime.BaseAPI {
867
867
  * Delete an item. If the item is an item shared with the current user, the corresponding share is deleted together with the item.
868
868
  * Delete an item
869
869
  */
870
- itemsIdDelete(id, meecoDelegationId, meecoOrganisationId, initOverrides) {
870
+ itemsItemIdDelete(itemId, meecoDelegationId, meecoOrganisationId, initOverrides) {
871
871
  return __awaiter(this, void 0, void 0, function* () {
872
- yield this.itemsIdDeleteRaw({ id: id, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
872
+ yield this.itemsItemIdDeleteRaw({ itemId: itemId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
873
873
  });
874
874
  }
875
875
  /**
876
- * Retrieve a specific Item by `id`.
877
- * Get Item
876
+ * Retrieve a specific Item by `item_id`.
877
+ * Get item
878
878
  */
879
- itemsIdGetRaw(requestParameters, initOverrides) {
879
+ itemsItemIdGetRaw(requestParameters, initOverrides) {
880
880
  return __awaiter(this, void 0, void 0, function* () {
881
- if (requestParameters.id === null || requestParameters.id === undefined) {
882
- throw new runtime.RequiredError('id', 'Required parameter requestParameters.id was null or undefined when calling itemsIdGet.');
881
+ if (requestParameters.itemId === null || requestParameters.itemId === undefined) {
882
+ throw new runtime.RequiredError('itemId', 'Required parameter requestParameters.itemId was null or undefined when calling itemsItemIdGet.');
883
883
  }
884
884
  const queryParameters = {};
885
885
  const headerParameters = {};
@@ -897,7 +897,7 @@ class ItemsApi extends runtime.BaseAPI {
897
897
  }
898
898
  }
899
899
  const response = yield this.request({
900
- path: `/items/{id}`.replace(`{${"id"}}`, encodeURIComponent(String(requestParameters.id))),
900
+ path: `/items/{item_id}`.replace(`{${"item_id"}}`, encodeURIComponent(String(requestParameters.itemId))),
901
901
  method: 'GET',
902
902
  headers: headerParameters,
903
903
  query: queryParameters,
@@ -906,23 +906,23 @@ class ItemsApi extends runtime.BaseAPI {
906
906
  });
907
907
  }
908
908
  /**
909
- * Retrieve a specific Item by `id`.
910
- * Get Item
909
+ * Retrieve a specific Item by `item_id`.
910
+ * Get item
911
911
  */
912
- itemsIdGet(id, meecoDelegationId, meecoOrganisationId, initOverrides) {
912
+ itemsItemIdGet(itemId, meecoDelegationId, meecoOrganisationId, initOverrides) {
913
913
  return __awaiter(this, void 0, void 0, function* () {
914
- const response = yield this.itemsIdGetRaw({ id: id, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
914
+ const response = yield this.itemsItemIdGetRaw({ itemId: itemId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId }, initOverrides);
915
915
  return yield response.value();
916
916
  });
917
917
  }
918
918
  /**
919
- * 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. ---
919
+ * 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. ---
920
920
  * Update an item
921
921
  */
922
- itemsIdPutRaw(requestParameters, initOverrides) {
922
+ itemsItemIdPutRaw(requestParameters, initOverrides) {
923
923
  return __awaiter(this, void 0, void 0, function* () {
924
- if (requestParameters.id === null || requestParameters.id === undefined) {
925
- throw new runtime.RequiredError('id', 'Required parameter requestParameters.id was null or undefined when calling itemsIdPut.');
924
+ if (requestParameters.itemId === null || requestParameters.itemId === undefined) {
925
+ throw new runtime.RequiredError('itemId', 'Required parameter requestParameters.itemId was null or undefined when calling itemsItemIdPut.');
926
926
  }
927
927
  const queryParameters = {};
928
928
  const headerParameters = {};
@@ -941,7 +941,7 @@ class ItemsApi extends runtime.BaseAPI {
941
941
  }
942
942
  }
943
943
  const response = yield this.request({
944
- path: `/items/{id}`.replace(`{${"id"}}`, encodeURIComponent(String(requestParameters.id))),
944
+ path: `/items/{item_id}`.replace(`{${"item_id"}}`, encodeURIComponent(String(requestParameters.itemId))),
945
945
  method: 'PUT',
946
946
  headers: headerParameters,
947
947
  query: queryParameters,
@@ -951,12 +951,12 @@ class ItemsApi extends runtime.BaseAPI {
951
951
  });
952
952
  }
953
953
  /**
954
- * 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. ---
954
+ * 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. ---
955
955
  * Update an item
956
956
  */
957
- itemsIdPut(id, meecoDelegationId, meecoOrganisationId, putItemsRequest, initOverrides) {
957
+ itemsItemIdPut(itemId, meecoDelegationId, meecoOrganisationId, putItemsRequest, initOverrides) {
958
958
  return __awaiter(this, void 0, void 0, function* () {
959
- const response = yield this.itemsIdPutRaw({ id: id, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId, putItemsRequest: putItemsRequest }, initOverrides);
959
+ const response = yield this.itemsItemIdPutRaw({ itemId: itemId, meecoDelegationId: meecoDelegationId, meecoOrganisationId: meecoOrganisationId, putItemsRequest: putItemsRequest }, initOverrides);
960
960
  return yield response.value();
961
961
  });
962
962
  }