You can let the CDI server create and sign the transaction with specified participants and attachments. This way, the
application server account connected to the application is the actual creator of the transaction.
Info |
---|
For the time being, the services "Monitor status", "Monitor status by participant" and "Multisign" are considered present in the CDICreateTransactionRequest and set to the value 'true'. |
Info |
---|
The Lequinox platform does not archive transactions for external role |
accounts or external accounts or external personal identities as they represent another organisation. If archiving these transaction events is needed, it must be tended to by the application. |
Error messagesexpand500 | - An unexpected error occurred: Type definition error[...]
- An unexpected error occurred: JSON parse error[...]
| These errors are returned if one or more parameters is of the wrong type.title | HTTP status code | Message | Comments |
---|
400 | Input not valid: Participant privateId 'XXXX' is not in the correct format. | Where 'XXXX' is the value for the 'privateId' parameter submitted in the request . |
400 | Input not valid: Participant corporateId 'XXXX' is not in the correct format. | Where 'XXXX' is the value for the 'corporateId' parameter submitted in the request . |
400 | Input not valid: Participant corporateId can not be null for corporate or server user. | 400 | Invalid role ID format | The parameters 'privateId' or 'corporateId' is incorrectly formatted. |
400 | Input not valid: Participant privateId can not be set for server user. | 400 | Input not valid: Participant corporateId can not be set for private user. | 400 | Input not valid: Participant corporateId can not be null for corporate or server user. | 400 | Input not valid: Participant can not be of unknown type: null | The parameter "type" is missing from /wiki/spaces/LPDA510/pages/1804027 |
400 | Input not valid: Participant privateId can not be null for private or corporate user. | 400 | Input not valid: Attachment fileName can not be empty | 400 | Input not valid: Attachment content can not be empty | 400 | Input not valid: Participant can not be of unknown type: null | 400 | Input not valid: Participant list can not be empty | 400 | Input not valid: Service package can not be empty | 400 | Unable to create transaction | The error is returned when a deactivated user is included as a participant in the transaction. |
500 | An unexpected error occurred: null | This error is returned when |