Errors and response codes

How Aera's REST APIs report success and errors, and where to find the response codes for each API.

🚧

Master: api-docs.aerahost.com

We're moving our API docs to docs.aera.id. Until the move is done, 19.1. Response Codes and 19.2. HTTP Error responses on api-docs.aerahost.com are the master for this page. If this page and api-docs differ, api-docs is right.

Aera's REST APIs return a responseInfo object in every JSON response.

FieldDescription
responseCode0 means success. Any other value is an error or a warning
timeStampWhen Aera answered, in UTC
messageA text explaining the code. Often empty on success
cidCorrelation ID. Include it when you contact support
externalResponseCodeA code from a third party, for example the acquirer, when there is one
Example error response
{
  "responseInfo": {
    "responseCode": "10000",
    "timeStamp": "2026-03-11T17:46:05.412Z",
    "message": "No report found with the provided file Id.",
    "cid": "1-67d06a5d-0e7c3b1f4c2a9d8e7f6a5b4c"
  }
}

HTTP status codes

StatusMeaning
400 Bad RequestThe request is malformed
401 UnauthorizedThe API key or access token is missing, wrong or expired
403 ForbiddenYou don't have access to this resource
404 Not FoundThe resource doesn't exist
405 Method Not AllowedThe HTTP method isn't allowed here
409 ConflictWhat you're adding already exists
413 Request Entity Too LargeThe request is too large
415 Unsupported Media TypeCheck Content-Type and Accept
429 Too Many RequestsYou sent too many requests in a short time. Wait, then try again
500 Internal Server ErrorAera couldn't handle the request
504 Gateway TimeoutAera didn't answer in time. Check the status before you try again

Error responses with a body include responseInfo. Responses for 403, 405, 413, 415, 429 and 504 have no body.

Response codes per API

APICodes
All REST APIsHTTP responses on api-docs.aerahost.com (full list)
Reporting APIGet report data (the ones you're most likely to see)
Terminal messages (Nexo)Response codes

Also see