API HTTP Error Messages
Overview of some common API error messages and what they mean.
Indicates that the request has not been applied because it lacks valid authentication credentials for the target resource.
Check the credentials are correct and are still valid (e.g. not expired)
Usually, when you see the 403 status code, the API request that is being made includes some form of authorisation. But server does recognise the authorisation credentials.
Another reason this status code might be returned is in case the user did not request an API access token with the correct permissions.
404 Server Error
Typical trigger for this error message is when website content has been removed or moved to another URL.
It could also be that the server responsible for the website is not running or the connection is broken.
429 Too Many Requests
The 429 Too Many Requests is one of the more common ones, and it's also self-explanatory. You are requesting data too often.
The limits are set by the API.
When possible, kleene will limit the requests we make to APIs to fit inline within these limits.
Advice is to try again later, or schedule your extracts at different times throughout the day, if this doesn’t work then contact [email protected]
- 500 Internal Server Error
- 502 Bad Gateway
- 503 Service Unavailable
- 504 Gateway Timeout
A 5** status usually means that the error is on the server (API) side, not on the user side of things (kleene). So the general advice is to:
- Try again later. The server might be under too much load at the moment
- Check the API status page, if one is available, for more information if there's maintenance going on, or the API is down
Note: A 5** error can also occur if system is not finding an incremental key. Run extract to a new destination table, or run as drop-create-load once then change back to Append. These actions can solve that issue.
Updated 2 months ago