Error responses
All reports API error responses share the same format: a message, an error code, the cause when there is one, and a traceability ID for support. Use this page to handle errors in your backend and to open a ticket with the data support needs.
{ "error": "<error message>", "error_code": "<error code>", "cause": "<error cause>", "traceability_id": "<request identifier>"}Fields
Section titled “Fields”| Field | Type | Description |
|---|---|---|
error |
string | Error message. |
error_code |
string | Error code, so you can handle the error in your backend. |
cause |
string | Cause of the error, when there is one. |
traceability_id |
string | Request identifier, so support can locate the exact request. |
Status codes
Section titled “Status codes”The reports API operations can respond with these errors, all in the format above:
| Code | Status | When |
|---|---|---|
400 |
Bad Request | A parameter is not valid (limit greater than 100 or not a number, page, since, or timeout with the wrong format) or the feedback body is not valid JSON. |
404 |
Not Found | There are no reports for the given application or transaction. |
500 |
Internal Server Error | Internal server error. |
The API reference details the responses of each operation.
Was this page helpful?
Thank you. We will use it to improve the documentation. If you want to tell us what is missing or unclear, write to support@ironchip.com.