Skip to content

too_many_requests: Amazon Creators API error

HTTP 429Token endpointDocumented by Amazon

What it means

You fetched new access tokens too often. A token is valid for an hour, so reuse it instead of fetching one per request.

Typical causes

  • A new token is fetched for every API call.
  • Several processes or containers each fetch their own token for the same Client ID.

How to fix it

  1. Cache the token until shortly before expires_in runs out.
  2. Share one cache across all processes using the same Client ID.
  3. Wait the seconds given in the Retry-After header.
  4. The official SDKs cache tokens automatically.

Not sure which part fails? Run Test credentials in the Scratchpad. It checks the token, the API access and the partner tag separately.

Example response

{
  "error": "too_many_requests",
  "error_description": "Your client has exceeded the token-endpoint rate limit. This usually indicates a missing token cache …"
}

Related errors

  • TokenExpired: Your access token is older than one hour. Fetch a new one and try again.
  • ThrottleException: You sent more requests than your limit allows, either per second or per day.