Groq API

Groq API errors and fixes

14 Groq API errors from the official error docs, grouped by HTTP status, each with what it means, why it happens, the documented fix and whether to retry. Verified October 18, 2026.

Error response body

The shape Groq API errors come back in, as the official docs show it. Read the status and error type from here before matching an entry below.

JSON

{
  "error": {
    "message": "String - description of the specific error",
    "type": "invalid_request_error"
  }
}

HTTP 400 Bad Request

400 Bad RequestThe server could not understand the request due to invalid syntax. The Python SDK raises BadRequestError.Retry? Not stated

HTTP 401 Unauthorized

401 UnauthorizedThe request lacks valid authentication credentials for the requested resource. The Python SDK raises AuthenticationError.Retry? Not stated

HTTP 403 Forbidden

403 ForbiddenThe request is not allowed due to permission restrictions. The Python SDK raises PermissionDeniedError.Retry? Not stated

HTTP 404 Not Found

404 Not FoundThe requested resource could not be found. The Python SDK raises NotFoundError.Retry? Not stated

HTTP 413 Content Too Large

413 Request Entity Too LargeThe request body is too large.Retry? Not stated

HTTP 422 Unprocessable Content

422 Unprocessable EntityThe request was well-formed but could not be followed due to semantic errors or model hallucinations. The Python SDK raises UnprocessableEntityError.Retry? Yes

HTTP 424 Failed Dependency

424 Failed DependencyThe request failed because a dependent request failed. This may occur when using Remote MCP in the case of authentication issues.Retry? Not stated

HTTP 429 Too Many Requests

429 Too Many RequestsToo many requests were sent in a given timeframe. Limits apply at the organization level across RPM, RPD, TPM, TPD, ASH, ASD and, for some organizations, ITPM and OTPM, and whichever threshold is reached first triggers the error. The Python SDK raises RateLimitError and retries it automatically.Retry? Yes

HTTP 498

498 capacity_exceededCustom Groq status code (Flex Tier Capacity Exceeded) returned when the flex service tier is at capacity and the request will not be processed. Flex requests fail quickly with status 498 and error capacity_exceeded.Retry? Yes

HTTP 499

499 Request CancelledCustom Groq status code used on the console logs page to signify that the request was cancelled by the caller.Retry? Not stated

HTTP 500 Internal Server Error

500 Internal Server ErrorA generic error occurred on the server. Requests that return server error codes are not charged. The Python SDK raises InternalServerError for status codes 500 and above and retries them by default.Retry? Yes

HTTP 502 Bad Gateway

502 Bad GatewayThe server received an invalid response from an upstream server. This may be temporary. Requests that return server error codes are not charged.Retry? Yes

HTTP 503 Service Unavailable

503 Service UnavailableThe server is not ready to handle the request, often due to maintenance or overload. Requests that return server error codes are not charged.Retry? Yes

No HTTP status

APIConnectionErrorRaised by the Groq Python SDK when it cannot connect to the API, for example due to network connection problems or a timeout. On timeout the subclass APITimeoutError is raised; requests time out after 1 minute by default.Retry? Yes

Newsletter

One email per week. New model releases, API changes, what broke, and how developers are working around it.