> For the complete documentation index, see [llms.txt](https://docs.moneroo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.moneroo.io/introduction/errors.md). # Errors Moneroo API is RESTful and as such, uses conventional HTTP response codes to indicate the success or failure of requests. This section describes the summary of these codes and what they mean in our context. ### Summary * Codes in the **2XX** range mean that the API request was processed successfully. * Codes in the **4XX** range mean that something was wrong with the data that you sent. For example, you might have missed some required parameters/headers, or you might be using the wrong API credentials. * Codes in the **5XX** range indicate an error in processing on our end ### Common HTTP Codes

Code	Description
200	OK - Request was successful
201	Created - The request was successful, and a resource was created as a result
202	Accepted - Request has been accepted and acknowledged. We will now go ahead to process the request and notify you of the status afterwards.
400	Bad Request - Malformed request or missing required parameters
401	Unauthorized - Missing required headers, wrong Public or Secret Key etc
403	Forbidden - You are trying to access a resource for which you don't have proper access rights.
404	Not Found - You are trying to access a resource that does not exist
422	Unprocessable Entity - You provided all the required parameters but they are not proper for the request
429	Too Many Requests - You have exceeded the number of requests allowed in a given time frame.
500	Internal Server Error - We had a glitch in our servers. Retry the request in a little while or contact support. Rarely happens.
503	Service Unavailable – We are temporarily offline for maintenance. Please try again later. Rarely happens.

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.moneroo.io/introduction/errors.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.