What do common API errors mean?
When something goes wrong with a Meta Model API request, the API returns an HTTP status code indicating the type of problem. Here is what the most common errors mean and how to resolve them.
400 — Bad request
Your request is malformed or contains invalid parameters. Check that your request body is valid JSON and that all required fields are included. See the API reference for the correct request format.
401 — Unauthorized
Your API key is missing, invalid, or has been revoked. Verify that you are including a valid API key in the Authorization header. If your key was recently revoked, generate a new one from the API keys page.
403 — Forbidden
Your account does not have permission to access the requested resource. This can occur if your account has been suspended or if you are trying to access a model that is not available to your team. Check your account status and review any warnings you may have received.
429 — Too many requests
You have exceeded your rate limit. The API will accept requests again once your usage drops below the limit. Implement exponential backoff in your retry logic — wait progressively longer between retries rather than retrying immediately. See What are the Model API rate limits? for more details.
500 — Internal server error
An unexpected error occurred on the server side. These are typically transient — wait a few seconds and retry. If the error persists, check the status page for any ongoing incidents, or contact support.
503 — Service unavailable
The API is temporarily overloaded or undergoing maintenance. Retry after a brief wait. If this persists, check for announcements on the status page.
For technical details on error response formats, authentication setup, and retry patterns, see the developer documentation.