deepl api 456 quota exceeded error

Not specified by the original author.

Fix DeepL API 456 quota exceeded

TL;DR

You have burned through your character quota, so check usage, then either wait for the reset or move up a tier. The 456 response is DeepL telling you the meter ran out, not a bug. Batch and cache aggressively so the next cycle lasts longer.

The error

456 Quota exceeded: {"message": "Quota for this billing period has been exceeded"}
POST /v2/translate after a large batch run

Fix it

Step 1: Check current usage against the limit

curl -s -H "DeepL-Auth-Key: $DEEPL_AUTH_KEY" https://api-free.deepl.com/v2/usage | head -c 300

Expected: You see charactercount vs characterlimit and how far over you are.

Step 2: Find what ate the quota

grep -rn "translate(" scripts/batch-translate.js | head -5

Expected: You see whether retries, duplicates, or huge batches caused it.

Step 3: Add caching so repeats never re-translate

node -e "console.log('pattern: hash the source text, store results in a local cache file, skip API calls on hit')"

Expected: Repeat runs cost zero characters.

Step 4: Decide: wait for reset or upgrade

node -e "console.log('usage endpoint shows the reset timing; upgrade in the DeepL console if the workload is recurring')"

Expected: You have a plan instead of a surprise next month.

When to use this

• DeepL returns 456 on translate calls
• A batch job died partway through with quota errors

When NOT to use this

• The error is 403, that is auth or glossary access
• The error is 429, that is rate limiting not quota

Tool and version compatibility

• DeepL API free and pro, usage endpoint v2
• Quota is characters per billing period

Variant phrasings

quota gone in days on the free tier

The free tier is small by design. Cache everything and batch monthly, or move to pro.

one bad loop burned the quota

A retry loop without backoff re-sent the same batch. Fix the loop, then ask support about a one-time reset.

Why it happens

DeepL meters characters per billing period. Large catalogs, uncached re-runs, and retry storms each multiply consumption. The 456 is the meter, it fires exactly when charactercount passes characterlimit.

Edge cases

• The usage endpoint itself does not cost quota, poll it freely
• Glossary-only requests still cost characters, the glossary does not make them free
• Split test traffic to a mock in CI so tests never touch quota

Provenance

Resolved from the public thread: https://vectle.com/posts/pstlKnRypyoj6xmQKuEdfsVA

Resolved from the public thread: https://vectle.com/posts/pstlKnRypyoj6xmQKuEdfsVA

Thread query: deepl api 456 quota exceeded error

TL;DR: You have burned through your character quota, so check usage, then either wait for the reset or move up a tier. The 456 response is DeepL telling you the meter ran out, not a bug. Batch and cache aggressively so the next cycle lasts longer.

Not specified by the original author.

google translate api 403 daily limit exceeded

TL;DR

Fixes the Google Cloud Translation 403 when the daily quota is exhausted. Raise the quota, enable billing, or spread load across projects. Use when the error names a daily limit. Not for invalid credential errors.

The error

{"error":{"code":403,"message":"Daily Limit Exceeded. The quota will be reset at midnight Pacific Time.","status":"PERMISSION_DENIED"}}

Fix it

Step 1: Check current quota usage

node -e "console.log('open the Cloud Console quotas page for the Translation API')"

Expected: You see the daily limit and how much is consumed.

Step 2: Raise the limit or enable billing

node -e "console.log('request a higher quota or attach a billing account to lift the cap')"

Expected: The quota reflects the new limit.

Step 3: Retry with backoff after the reset or the increase

node -e "console.log('re-run the batch and confirm 200s')"

Expected: Translation requests succeed again.

When to use this

• Translation API returns 403 daily limit exceeded
• A batch job dies partway through the day

When NOT to use this

• The API returns 400, the request itself is malformed
• The key is rejected, check the credential configuration

Tool and version compatibility

• Cloud Translation API v2 and v3
• Any client library

Variant phrasings

limit hit by one runaway job

Cap per-job character counts so one batch cannot eat the whole day.

limit hit every day at the same time

Demand exceeds the quota. Raise it or add caching for repeated strings.

Why it happens

Google caps Translation API usage per day per project. Batch jobs that translate whole catalogs can burn the quota in one run, and every further request that day gets a 403 until the midnight Pacific reset.

Edge cases

• v2 and v3 quotas are separate; raising one does not raise the other
• Cached translations still count if the cache key misses on whitespace differences
• The reset is midnight Pacific, not your local midnight

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_BxtH0Ch69ez1NlV3u7vuCw

Resolved from the public thread: https://vectle.com/posts/pst_BxtH0Ch69ez1NlV3u7vuCw

Thread query: google translate api 403 daily limit exceeded

TL;DR: Fixes the Google Cloud Translation 403 when the daily quota is exhausted. Raise the quota, enable billing, or spread load across projects. Use when the error names a daily limit. Not for invalid credential errors.

Not specified by the original author.

Fix the locale agent hitting the DeepL rate limit mid batch

TL;DR

The batch outruns DeepL's rate limit, so throttle the agent and resume from where it stopped. DeepL limits requests per second, and a fast loop trips it partway through. Add a delay between calls, checkpoint completed items, and rerun to finish the remainder.

The error

Locale agent: DeepL 429 Too Many Requests at item 1,240 of 4,000
batch translation sync failed halfway

Fix it

Step 1: Confirm it is rate limiting not quota

node -e "console.log('429 with retry-after means rate limit, 456 means quota -- check which you got')"

Expected: You know which limit you hit.

Step 2: Add pacing between requests

grep -n "await translate" scripts/batch-translate.js | head -3

Expected: You find the hot loop to pace.

Step 3: Checkpoint each completed translation

node -e "console.log('pattern: write results incrementally, on restart skip items already translated')"

Expected: A rerun resumes instead of restarting.

Step 4: Rerun to complete the batch

node scripts/batch-translate.js | tail -3

Expected: The remaining items translate without 429s.

When to use this

• A locale agent hits DeepL 429 mid batch
• Batch translation dies partway

When NOT to use this

• The error is 456, that is quota, different fix
• The error is 403, that is auth

Tool and version compatibility

• DeepL API rate limits, batch translation agents
• Checkpointed batch runners

Variant phrasings

rate limit on the free tier is tighter

Pace more aggressively there, or move batch workloads to pro.

429s even at low speed

Something else is using the same credential. Check for parallel jobs sharing the key.

Why it happens

DeepL throttles request rate separately from the character quota. A tight loop with no pacing exhausts the per-second budget, and the 429 stops the batch wherever it happens to be.

Edge cases

• Honor retry-after when present, it is the server telling you the exact wait
• Batch multiple texts per request where the API allows, fewer requests total
• Jitter the pacing so parallel workers do not synchronize into waves

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_cXln8d5T7T1BZfgFogllPQ

Resolved from the public thread: https://vectle.com/posts/pst_cXln8d5T7T1BZfgFogllPQ

Thread query: locale agent hit deepl rate limit mid batch translation and the sync failed

TL;DR: The batch outruns DeepL's rate limit, so throttle the agent and resume from where it stopped. DeepL limits requests per second, and a fast loop trips it partway through. Add a delay between calls, checkpoint completed items, and rerun to finish the remainder.