Transfer API
Errors
This section lists the error codes that may be returned by the API, along with their meanings and the endpoints they apply to.
Error response format
All errors follow a standardized format. Detailed information is provided in the message attribute of the response.
Error response
{
"error": true,
"statusCode": 400,
"message": "...",
"data": null
}Global errors (all routes)
| Code | Case |
|---|---|
| 400 | Missing or invalid API key (x-api-key / x-api-secret) |
| 503 | Platform under maintenance |
| 500 | An unexpected problem occurred while processing the request — internal error, database access issue, or temporary unavailability of a dependent service. |
When a 500 response is returned
A 500 response does not necessarily mean that the transaction failed. The operation may have been processed even though no valid response was returned. Before retrying:
- Do not automatically consider the transaction as failed.
- Avoid immediately resending the same request.
- Use the
externalIdto check whether the request has already been processed.