rate-limited

rate-limited

HTTP 429 Too Many Requests
Content-Type: application/problem+json

{
  "type": "https://docs.transmute.403fin.io/errors/rate-limited",
  "title": "...",
  "status": 429,
  "detail": "...",
  "requestId": "req_01J..."
}

Your per-second token bucket is exhausted. This is about request rate; the monthly quota is a separate mechanism (quota-exceeded).

Common causes

• A burst of parallel requests beyond your plan's requests-per-second
• A retry loop without backoff amplifying itself

How to fix it

Honor Retry-After (seconds) and back off. Watch RateLimit-Remaining on every response to pace proactively — see Rate Limits & Quotas. Rate-limited requests are never billed, so backing off costs nothing but latency.

Does it bill?

No — rejected before the engine runs. See Test vs Live Keys for the full billing rules.

Related

• Errors Overview — the problem+json shape and the closed catalog
• Every response carries an X-Request-Id; quote it when contacting support.