How an error looks
error, never on message. A malformed request answers with message as a list of every parameter to fix:
error_description, or a bare {"message": "..."}, comes from the gateway before the request reaches the API: check the bearer token (Sandbox and authentication).
Not found
An id that does not exist and an id outside your account answer the same way, so a caller never learns what exists.Bad requests
A query parameter the API does not know is ignored, not refused: check the spelling of a filter that seems to have no effect.
Limits and faults
Treat a code you do not recognise as a refusal of that call.
What is safe to retry
Every operation of this API is aGET: all are safe to repeat.
Getting help
When you contact Securitize about a response, send the operation and the time of the call, the ids involved (tokenId, deposit or transaction id, tokenIssuanceId, eventId), and the error, message and statusCode you received. Never send your client secret or your webhook signing secret.