Unbabel · Rate Limits

Unbabel Rate Limits

Unbabel does not publish fixed numeric rate limits for the Translation API (tapi/v2) in its public developer documentation. Because translation is an asynchronous, enterprise, quote-based service, throughput is governed in practice by the customer's contracted translation volume/commitment rather than by a documented per-second or per-minute request cap. Submitting a translation returns immediately with a job uid; clients then poll the translation/{uid} endpoint or receive a callback, so polling should be reasonable and backed off rather than tight-looped.

Unbabel Rate Limits is the machine-readable rate-limit profile for Unbabel on the APIs.io network, in the API Commons Rate Limits shape.

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

An exhausted limit returns HTTP 429.

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.

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

Tagged areas include Translation, LangOps, Rate Limiting, and Quotas.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-07-03.
Written by API Evangelist on 2026-07-03 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
TranslationLangOpsRate LimitingQuotas

Limits

Translation API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the tapi/v2 API.
Translation Volume account
words
per contract
Effective throughput is bounded by the customer's committed/quoted monthly translation volume.
Job Status Polling account
requests
not published
Poll translation/{uid} with backoff, or use a callback_url, since jobs complete asynchronously.

Policies

Asynchronous Processing
Translation and mt_translation submissions return a job uid immediately; results are retrieved later by uid or delivered to a callback URL.
Backoff Strategy
Clients should poll job status with exponential backoff and honor Retry-After on any 429 responses.

Sources

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/unbabel-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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