> For the complete documentation index, see [llms.txt](https://docs.sfox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sfox.com/errors/error-codes.md). # Error Codes ## HTTP Status Codes The sFOX API communicates error codes through HTTP status codes. The following are the error codes currently in use:

Code	Description
`400`	Bad Request — Your request was malformed in some way
`401`	Unauthorized - Your API key is wrong
`403`	Forbidden — The API key is not authorized for this endpoint
`404`	Not Found — The specified endpoint could not be found
`405`	Method Not Allowed — You tried to access a endpoint with an invalid method
`406`	Not Acceptable — You requested a format that isn’t json
`422`	Unprocessable Entity - Your request contained invalid input
`429`	Too Many Requests — You have exceeded your request limit
`500`	Internal Server Error — We had a problem with our server. Try again later.
`503`	Service Unavailable — We’re temporarily offline for maintanance. Please try again later.

--- # 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.sfox.com/errors/error-codes.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.