Weblate Rate Limits
Weblate's REST API implements request throttling based on authentication status. Anonymous (unauthenticated) requests face heavy throttling to encourage API token usage. Authenticated requests using personal access tokens or project-scoped tokens have significantly higher limits. Rate limit status is communicated via response headers. Limits can be configured for self-hosted instances via Django REST framework settings or Docker environment variables.
Weblate Rate Limits is the machine-readable rate-limit profile for Weblate on the APIs.io network, in the API Commons Rate Limits shape.
It captures 3 rate-limit definitions.
Limit state is signalled in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
Tagged areas include Localization, Translation, Internationalization, Open Source, and Continuous Localization.
X-RateLimit-LimitX-RateLimit-RemainingX-RateLimit-Reset
generated.
Limits
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.