# Errors Wundaflow uses standard HTTP response codes to indicate success or failure of an API request. Generally, codes in the `2xx` range indicate success, codes in `4xx` range indicate an error that failed due to the request params, and codes in the `5xx` range indicate an error with Wundaflow's platform. Most `4xx` error codes will also return a JSON response body that indicates the exact issue with the request.
HTTP statusSummary
200 - OKEverything was OK.
400 - Bad RequestRequest was not accepted, often due to missing or incorrect params.
401 - UnauthorizedMissing, revoked or invalid API key.
402 - Request FailedThe params provided were valid but the request failed.
403 - ForbiddenAPI key provided does not have permission to perform the requested action.
404 - Not FoundThe requested resource could not be found.
409 - ConflictThe request conflicts with another request or the resource is not in the correct state.
429 - Too Many RequestsYou are being rate limited, slow down your requests or ask for a rate increase.
500 - Server ErrorSomething is wrong on Wundaflow's side. Try the request again or contact support.
--- # 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.wundaflow.com/api/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.