Too Many Requests (429)

Your partner account went over its quota for the current minute (600 requests per minute across all your keys, fixed window). The request was not processed — nothing was created, nothing was queued.

Every response to a call made with your key tells you where you stand: RateLimit-Limit (the quota), RateLimit-Remaining (calls left in this window) and RateLimit-Reset (seconds until the window resets). Pace bulk work on RateLimit-Remaining instead of waiting for a 429.

What to do: wait the number of seconds in the Retry-After header and repeat the request. For a POST, reuse the same Idempotency-Key you sent; a GET is simply repeated. Spread bulk work (imports, backfills) over time instead of bursting it; the gateway also has a global throttle that every partner shares.

A 429 whose body is only {"message":"Too Many Requests"}, with no Retry-After and no request_id, comes from that shared gateway throttle, not from your quota. Back off exponentially, starting at about one second, and log the UTC time and the operation instead of a request_id. See API errors.

If you need a higher quota, contact support with your partner id.