SimpleLocalize · Rate Limits

Simplelocalize Rate Limits

SimpleLocalize publishes plan-level capacity (translation keys, seats, auto-translation character pools) on its pricing page but does not document numeric request-per-second/minute API rate limits or rate-limit response headers in publicly reachable documentation. Plan caps belong in the plans artifact; this artifact is left as a low-confidence stub until SimpleLocalize publishes per-key request limits.

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

It captures 3 rate-limit definitions, measuring varies.

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

Tagged areas include Localization, Translation, Internationalization, and Rate Limiting.

3 Limits Throttle: 429
LocalizationTranslationInternationalizationRate Limiting

Limits

Per-Account Request Throttling account
varies
see SimpleLocalize API documentation
Numeric per-second / per-minute request limits are not published on the pricing page.
Translation Keys (Plan Cap) account
varies
plan-dependent (250 / 1,000 / 4,000 / 12,000)
Plan-tier caps; tracked authoritatively in plans/simplelocalize-plans-pricing.yml.
Auto-Translation Character Pool account
varies
plan-dependent monthly top-up with rollover ceiling
Soft consumption cap on machine-translation characters; plan tier sets the ceiling.

Policies

Plan-Tier Quotas
Capacity limits (translation keys, seats, languages, auto-translation characters) are enforced at plan level and published on the pricing page.
Backoff
When request-rate throttling does occur, clients should implement exponential backoff with jitter and honor any Retry-After header the API returns.

Sources