# Error handling The API returns standard HTTP status codes to indicate success or failure: * `200 OK` – Request succeeded * `201 Created` – Resource successfully created * `400 Bad Request` – Invalid input or parameters * `401 Unauthorized` – Missing or invalid API key * `403 Forbidden` – You don't have permission to perform this action * `404 Not Found` – Resource does not exist * `429 Too Many Requests` – Rate limit exceeded * `500 Internal Server Error` – Something went wrong on our end Error responses include a JSON payload with a `message` field explaining what went wrong. Make sure your integration handles these errors gracefully and logs or displays useful feedback to users where appropriate. --- # 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://developer.rogerroger.io/getting-started/error-handling.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.