Weblate · Rate Limits

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, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions.

Tagged areas include Localization, Translation, Internationalization, Open-Source, and Continuous Localization.

3 Limits
LocalizationTranslationInternationalizationOpen-SourceContinuous LocalizationVersion Control

Limits

Anonymous Request Limit global
Authenticated Request Limit per-user
Pagination Limit per-request

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/weblate-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.