SYSTRAN · Rate Limits

Systran Rate Limits

SYSTRAN does not publish a fixed public per-minute request-rate limit for the Translate API. Practical throughput is governed by the character allowance of your subscription (metered per character, starting with the 500,000-character free trial) rather than by a documented requests-per-second cap. Large or long-running documents are handled through the asynchronous file translation flow (async=true) and batches, which decouple job submission from a per-request size limit. Per-request text size, concurrency, and account-level throughput ceilings are enforced by SYSTRAN but are not published as fixed numeric values.

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

It captures 4 rate-limit definitions, measuring requests, characters, and jobs.

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

Tagged areas include Machine Translation, Translation, NLP, Rate Limiting, and Quotas.

4 Limits Throttle: 429
Machine TranslationTranslationNLPRate LimitingQuotas

Limits

Translate API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the Translate API.
Character Allowance account
characters
per subscription (500,000 on the free trial)
Usage is metered per character; throughput is bounded by your plan's character allowance.
Synchronous Text Size request
characters
bounded per request
Very large content should use asynchronous file translation instead of a single synchronous text call.
Asynchronous File Jobs account
jobs
managed via batches
Large or long-running documents are submitted with async=true and polled by requestId; batches group multiple requests.

Policies

Asynchronous Processing
Submit large documents with async=true and poll /translation/file/status by requestId; group multiple jobs into a batch.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Character Metering
Billing and effective throughput are driven by characters translated rather than a per-second request cap.

Sources