Tolgee · Rate Limits

Tolgee Rate Limits

Tolgee does not publish a single fixed numeric REST API rate-limit table. On self-hosted open-source deployments, throughput is bounded only by the operator's own infrastructure and any reverse-proxy limits they configure. On Tolgee Cloud (app.tolgee.io), practical limits are governed by plan quotas - translation keys, seats, and machine-translation (MT) credits - rather than by a published requests-per-second ceiling, and Tolgee may apply abuse-protection throttling. Treat the values below as quota-style limits and verify specifics with Tolgee for high-volume automation.

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

It captures 4 rate-limit definitions, measuring keys, seats, credits, and requests.

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

Tagged areas include Localization, i18n, Translation, Open Source, and Developer Tools.

4 Limits Throttle: 429
Localizationi18nTranslationOpen SourceDeveloper ToolsRate LimitingQuotasThrottling

Limits

Translation Keys (quota) account
keys
per plan (e.g. 500 Free, 2000 Team, 5000 Business, 20000 Advanced)
A key is counted once regardless of how many languages it is translated into.
Seats (quota) account
seats
per plan (e.g. 3 Free, 4 Team, 8 Business, 20 Advanced; up to 10 self-hosted free)
Number of team members who can access projects.
MT Credits (quota) account
credits
per plan (e.g. 10000 included on Free)
Roughly 1 credit per translated character for MT providers; LLM token-based for AI features.
REST API Requests account
requests
see provider documentation
No fixed published per-second/per-minute limit; cloud may apply abuse-protection throttling, self-hosted bound by operator infrastructure.

Policies

Plan Quotas
Cloud usage is gated by key, seat, and MT-credit allowances per subscription tier; overages are billed pay-as-you-go where a card is on file.
Self-Hosted Operator Control
Open-source self-hosted deployments enforce only the limits the operator configures at the proxy or application layer.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on HTTP 429 responses.

Sources