How the Isaacus API communicates errors
2xx
range indicate success, codes in the 4xx
range indicate a problem with the request that was sent, and codes in the 5xx
range indicate an error with our servers.
Errors returned by our API servers (as opposed to errors generated by gateway servers) will conform to the RFC 7807 problem detail standard:
400 Bad Request
status code.
A validation error should always include a non-generic detail
field that explains, in some way, what was wrong with the request. If you ever encounter a validation error that does not include a detail
field (or that lacks sufficient information to help you understand what went wrong with your request), please let us know.
401 Unauthorized
status code.
If you encounter an unauthenticated error, please double-check that the API key you are using to make the request is correct and active. If you are certain that the API key is correct and active, please let us know.
402 Payment Required
status code.
If you encounter a payment required error but you have no outstanding balance, please let us know.
403 Forbidden
status code.
If you encounter an access forbidden error but you have not unsubscribed from our API plan, please let us know.
404 Not Found
status code.
If you encounter a not found error, please double-check the URL you are using to make the request. If you are certain that the URL is correct, please let us know.
GET
request to an endpoint that only supports POST
requests.
A method not allowed error will return the 405 Method Not Allowed
status code.
413 Payload Too Large
status code.
If you want to be able to send larger requests, please let us know.
500 Internal Server Error
status code.
You are advised to try retrying your request if you encounter an internal server error. If the problem persists, please let us know, or else try waiting a bit later, as we are pinged whenever internal server errors occur and we may be in the process of fixing the problem.