Amazon Translate vs SYSTRAN Translate API

Amazon Translate

IAM policies scope access per action and resource, with a TranslateReadOnly managed policy, and CloudTrail logs each call. AWS may store and use text to improve Amazon AI services unless the organisation sets an opt-out policy.

SYSTRAN Translate API

Five documented REST APIs cover text, files, dictionaries, translation memories and profiles, with a Google-compatible mode and a public price of €14.99 per million characters. The reference pages date from June 2023, and no changelog, status page, rate limit, SDK or downloadable OpenAPI file was found. The terms bar benchmark tests and automated use beyond human volumes.

Amazon Translate

1. Chunk real-time text under 10,000 bytes, not characters, so multibyte scripts fit less per call
2. Pass SourceLanguageCode auto to detect the source language, and handle DetectedLanguageLowConfidenceException
3. Read AppliedSettings in the response, since unsupported formality or profanity settings are dropped without an error
4. Retry TooManyRequestsException with backoff, which the AWS SDKs do by default
5. Set the AI services opt-out policy before sending private text

SYSTRAN Translate API

1. Send the key as Authorization: Key <api_key> and avoid the documented ?key= query option, which puts the secret in URLs and logs
2. Expect HTTP 400, not 401, when credentials are missing. The body reads No key / credentials provided
3. Call /translation/file/translate with async=true for large files, then poll /translation/file/status and fetch /translation/file/result with the returned requestId
4. Apply dictionaries and translation memories through a profile and pass its UUID as profile. withDictionary and withCorpus are deprecated
5. Read the terms before automating. They bar benchmark tests and request volumes beyond normal human use, and SYSTRAN may throttle or suspend access