...
| Type | Name | Description | Qualification | Schema |
|---|---|---|---|---|
| Body | request | Request body parameters, see schema for details. | Required |
Responses
| HTTP Code | Common messages | Description | Schema |
|---|---|---|---|
| 200 | Contains status and timestamp information for when the participant opened and signed the transaction. | ||
| 400 | The application with the specified key could not be found | string | |
| Unknown error | This error message is returned when
| string | |
| Input not valid: Transaction can not be empty | This error message is returned when the parameter 'transaction' is missing in ManagedUserTransactionRequest. | string | |
| Invalid role ID format | The parameters 'corporateId' or 'applicationAccessId' or 'privateId' in User are not in the correct format. | string | |
| Input not valid: Participant can not be null. | This error message is returned when the user parameter is not mentioned in ManagedUserTransactionRequest. | string | |
| Input not valid: Participant can not be of unknown type: null | This error message is returned when
| string | |
| Input not valid: Participant corporateId can not be null for corporate or server user. | string | ||
| Input not valid: Participant applicationAccessId can not be null for private or corporate user. | string | ||
| Input not valid: Participant privateId can not be null for private or corporate user. | string | ||
| Managed identity was not found | The parameters 'corporateId' or 'applicationAccessId' or 'privateId' in User is incorrect. | string | |
| 500 | An unexpected error occurred: Type definition error: <…> | This error message can be returned if one or more parameters are of the wrong type. | string |
| An unexpected error occurred: JSON parse error: <…> | This error message can be returned if one or more parameters are of the wrong type. | string |
Security
| Type | Name |
|---|---|
| apiKey | Key |
...