quota-exceeded

quota-exceeded

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

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

The pool your credential draws from is exhausted. Which pool depends on the key — and, on paid plans, on your own spend-cap settings:

• Test key (tk_test_) — your account's one-time 250-request test allowance is spent. It is shared by all your test keys, applies on every plan (paid included), and never resets; the detail names the allowance and carries no reset date. Continue with a live key.
• Live key (tk_live_) on a hard-stop plan (Free) — the quota (1,000 conversions) is spent. The detail names the quota and the reset time (the start of the next period). Paid plans without caps never see this — they meter overage instead of blocking.
• Live key on a paid plan with a self-serve cap (Spend Caps) — either the no-overage hard stop is on and your included volume is used up, or your overage spend cap is reached. The detail says which; turn the cap off / raise it on the billing page, or upgrade.

X-Quota-Limit tells you which pool you're drawing from: 250 is the test pool; anything else is your plan's included volume.

Common causes

• Development or CI still pointed at a test key after the evaluation allowance ran out
• The Free tier's 1,000 live conversions/month spent
• A runaway loop consuming quota

How to fix it

• Test key: create a live key — the free plan includes 1,000 live conversions/month, so switching costs nothing.
• Live key on Free: upgrade in the portal for a higher allowance with metered overage, or wait for the monthly reset.
• Watch X-Quota-Remaining on every metered response (and test_remaining in GET /v1/usage) to see either limit coming.

Does it bill?

No — quota rejections are never billed or counted. 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.