# Errors When your API request cannot be completed successfully, the response provides information about the failure in the message body and the HTTP status code. For validation errors, Beta provides details of what failed, including the field that failed validation and the problem with it. Some of the status codes we return are listed below. | Code | Title | Description | | ---- | --------------------- | ----------------------------------------------------------------------------------------------------------------- | | 400 | Bad Request | The server cannot process the request because it is inadequately formed. | | 401 | Unauthorised | The API key is invalid. | | 403 | Forbidden | The API key doesn't have appropriate permissions for the request. | | 404 | Not Found | You requested an object or page that could not be found. | | 429 | Too Many Requests | The rate limit was exceeded i.e. the server received too many requests in a given period of time. | | 500 | Internal Server Error | The server encountered an error. Try again later. | | 503 | Service Unavailable | The server is unable to handle the request due to a temporary overload or scheduled maintenance. Try again later. | --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.betaramps.com/documentation-beta-ramps/api-guide/errors.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.