When interacting with the API, you might encounter various error codes. These codes are meant to help you understand and troubleshoot issues effectively. The following section outlines the most frequently encountered error types.
For more general information about error codes we suggest the external Mozilla guides to client error status codes (errors that begin with the number 4) and server error status codes (errors that begin with the number 5).
400 Bad Request
The request you made to the API was malformed or contained invalid parameters. Double-check your input and try again.
You lack the necessary authentication credentials for the requested resource. Make sure that your API token has been set correctly and that it has not expired.
A token is considered expired if it has not been used for authenticating an Ardoq API request in the last 60 days. Once expired, a new token must be generated. You can read more about how to view and manage your tokens in this guide.
Your request is valid, but you're not authorized to access the requested resource. Review your permissions or contact your administrator.
404 Not Found
The requested resource could not be located on the server. Verify the URL and try a different endpoint if needed.
There's a conflict with the current state of the resource. This might occur if you're trying to create a resource that already exists.
422 Unprocessable Content
Your request was understood, but it contains semantically incorrect or incomplete information. Check your data and try again.
429 Too Many Requests
You've exceeded the rate limit for API requests. Slow down your requests to avoid this error. Every 429 response includes an HTTP header
Retry-After with a value indicating the number of seconds that you should wait before attempting a new request.
Rate limiting is a technique used to regulate the number of requests that can be made to an API within a certain time period. It helps us prevent abuse, maintain fair usage, and protect the overall quality of service.