Weglot · Rate Limits

Weglot Rate Limits

The primary usage constraint on the Weglot API is the per-plan translated-word allowance (and the included number of languages), not a published per-second request rate. Word allowance is consumed as unique content is translated, and a project that exceeds its plan allowance stops translating new content (or auto-upgrades to the next tier when enabled). Weglot does not publish explicit per-minute / per-second request quotas for the translate or public endpoints; specific request-rate values are not reconciled in this artifact.

Weglot Rate Limits is the machine-readable rate-limit profile for Weglot on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring words, languages, and requests.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Translation, Localization, Internationalization, Machine Translation, and Multilingual.

3 Limits Throttle: 429
TranslationLocalizationInternationalizationMachine TranslationMultilingualRate LimitingQuotasThrottling

Limits

Translated Word Allowance project
words
per plan (2,000 to 5,000,000; custom on Enterprise)
Unique words translated across the project, counted once regardless of page views.
Translated Language Count project
languages
per plan (1 to 20; custom on Enterprise)
Number of target languages a project may translate into.
Request Rate project
requests
see provider documentation
No explicit per-second/per-minute request rate is published for the translate or public endpoints.

Policies

Tiered Allowances
Word and language allowances increase as projects move up subscription tiers and via Enterprise agreements.
Auto-Upgrade
Projects can opt into automatic upgrade to the next plan when they exceed their current word allowance.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor any Retry-After header on 429 responses.

Sources