Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 11
Next »
HTTP status code | Message | Comments |
---|
400 | Input not valid: Participant can not be null. | This error message is returned if the 'user' parameter of ManagedUserTransactionRequest is missing. |
400 | Input not valid: Transaction can not be empty | This error message is returned if the 'transaction' parameter of ManagedUserTransactionRequest is missing or is empty. |
400 | An error has occurred | This error message is returned if the transaction data of ManagedUserTransactionRequest is not in the correct format. |
400 | Input not valid: Participant can not be of unknown type: null | This error message is returned if |
400 | Input not valid: Participant corporateId can not be null for corporate or server user. |
|
400 | Input not valid: Participant applicationAccessId can not be null for private or corporate user. |
|
400 | Input not valid: Participant privateId can not be null for private or corporate user. |
|
400 | Unknow error | This error message is returned if a wrong 'type' is specified for User. For example, a CORPORATE type is mentioned as SERVER. |
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. |