Errors DiVA API
The DiVA API uses standard HTTP response codes to indicate the status of requests. When errors occur, the API may return an error message. You can use the response codes and error messages to aid in debugging requests and to improve your exception handling capability. Core API error codes are listed separately.
Response codes
Copy section link
The DiVA API uses standard HTTP response codes to indicate the status of requests. In general, codes in the 2xx range indicate success, codes in the 4xx range indicate an error in the request, and codes in the 5xx range indicate an error on the Marqeta platform.
The following table shows some common response codes:
| Response Code | Description |
|---|---|
200 Successful |
Request completed successfully. |
202 Accepted |
Request accepted for asynchronous file export. A body of "Pending" indicates that processing of the file is underway. |
400 Bad Request |
Request is not properly formed. For example, the query filter syntax is incorrect. |
403 Forbidden |
Credentials do not authorize user to view the requested resource. |
404 Not Found |
Request URL is not properly formed. For example, the aggregation level path parameter is missing. |
410 Gone |
The requested file has expired and cannot be retrieved. Try exporting and then downloading the file again. |
429 |
Requests exceed rate limits, which accept a maximum of 300 report requests per five-minute interval (one per second). |
Error codes and messages
Copy section link
Error codes are based on HTTP response codes. The first three digits include the HTTP response code and the last three digits represent the error.
Common error codes 403
| Error Code | Description |
|---|---|
403001 |
Field forbidden exception |
403002 |
Filters forbidden exception |
403003 |
Program forbidden exception |