Versions Compared

Old Version 14

changes.mady.by.user Technical writer (Unlicensed)

Saved on

compared with

New Version 15

changes.mady.by.user Technical writer (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Info

The Lequinox platform does not archive transactions for external role accounts or external personal identities as they represent another organisation. If archiving these transactions is needed it must be tended to by the application.


Steps

  1. Submit a request in accordance with the details in Create transaction as a platform-managed user.
  2. The platform signs the create transaction request message on behalf of the platform-managed user.
  3. The platform creates the transaction.
  4. The platform archives the transaction details along with timestamps.
  5. The platform returns the TransactionResponse.


Plantuml


Error messages Moved to API endpoint page

Expand
title


HTTP status codeMessageComments
400The application with the specified key could not be found
400Invalid role ID formatThis error message is returned if the parameters 'corporateId', 'applicationAccessId' or 'privateId' in User are not in the correct format.  User can be either a 'creator' or 'participant' of ManagedUserCreateTransactionRequest.
400Input not valid: Attachment fileName can not be emptyThis error message is returned if the parameter 'fileName' is missing in Attachment of ManagedUserCreateTransactionRequest
   400Input not valid: Attachment content can not be emptyThis error message is returned if the parameter 'content' is missing in /wiki/spaces/LPDA510/pages/1804247of ManagedUserCreateTransactionRequest
400Input not valid: Participant can not be of unknown type: null

This error message is returned if

Participant can refer to either 'creator' or 'participant' parameter of ManagedUserCreateTransactionRequest

400Input not valid: Participant corporateId can not be null for corporate or server user.Participant can refer to either 'creator' or 'participant' parameter of ManagedUserCreateTransactionRequest
400Input not valid: Participant applicationAccessId can not be null for private or corporate user.Participant can refer to either 'creator' or 'participant' parameter of ManagedUserCreateTransactionRequest
400Input not valid: Participant privateId can not be null for private or corporate user.Participant can refer to either 'creator' or 'participant' parameter of ManagedUserCreateTransactionRequest
400Managed identity was not foundThis error message is returned if the parameters 'corporateId' or 'applicationAccessId' or 'privateId' in User are incorrect. User can be either a 'creator' or 'participant' of ManagedUserCreateTransactionRequest.
400Input not valid: Creator can not be empty
400Input not valid: Participant list can not be empty
400Input not valid: Service package can not be empty
500An unexpected error occurred: null

This error message is returned if

500

An unexpected error occurred: JSON parse error: [...]

An unexpected error occurred: Type definition error: [...]

These error messages are returned if one or more parameters are of the wrong type.