> For the complete documentation index, see [llms.txt](https://docs.birdie.so/birdie-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.birdie.so/birdie-docs/birdie-api/http-status-and-errors.md). # HTTP Status & Errors #### HTTP Status Code 200: Success The HTTP status code `200` indicates that a request has succeeded. This means that the server has successfully processed the client's request. *** **HTTP Status Code 400: Bad Request** A response with a `400` status code indicates that the request cannot be accepted. Might be because the request body is empty when it should not be. **HTTP Status Code 401: Authentication Error** A response with a `401` status code indicates that the API key is invalid, missing, or associated with a user who has been removed from your team. **HTTP Status Code 429: Too many requests** A response with a `429` status code indicates that you reached the maximum number of api calls within a minute timeframe. Wait a minute and retry. **HTTP Status Code 404: Resource not found** A response with a `404` status code indicates that the object you requested was not found. Try again with another request. **HTTP Status Code 500: Internal server error** A response with a `500` status code indicates an internal server error. There is maybe something wrong on Birdie backend… Reach out at --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.birdie.so/birdie-docs/birdie-api/http-status-and-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.