Public APIs
AI Translate text API favicon

AI Translate text API

Text Analysis

The Text Translation API translates text into any of the 80 supported languages, providing accurate and context-aware translations.

AI Translate text API's website screenshot

About AI Translate text API

Text Translation is an asynchronous text-translation API published by SharpAPI on ApyHub. A client submits content via a POST request, optionally including context to disambiguate terms, a language parameter specifying the source language, and a voice_tone parameter to steer style (for example, funny, joyous, or a named authorial voice). The submit call returns a job_id immediately rather than blocking until translation completes.

Job status is retrieved by polling a GET endpoint with the job_id, which reports one of four states: queued, running, success, or failed. Once a job succeeds, the response includes the translated content along with from_language and to_language fields identifying the source and target languages. The API documentation recommends polling at most once per second, as faster polling counts against rate limits without speeding up job completion.

The product is intended for use in content pipelines, multilingual support workflows, or batch translation jobs where non-blocking, asynchronous processing is needed. The current version is 1.0.0, with two endpoints (submit and status check) covering POST and GET methods.

Key features

  • Asynchronous text translation via submit-then-poll job pattern
  • Optional context parameter to disambiguate terms during translation
  • Optional voice_tone parameter to steer style (e.g. funny, joyous, or a named author's voice)
  • Optional language parameter to specify source content language
  • Job status polling with queued/running/success/failed states
  • Returns translated content with from_language and to_language metadata

Frequently asked questions

How does the translation process work?

You submit content to a POST endpoint which returns a job_id immediately, then poll the GET status endpoint with that job_id until the job reaches a terminal state. When successful, the result includes the translated content plus from_language and to_language.

How often should I poll for job status?

Poll at most once per second; faster polling counts against your rate limit without finishing the job sooner.

Can I control the tone or style of the translation?

Yes, the optional voice_tone parameter lets you steer the output toward a style such as funny, joyous, or a named authorial voice.

Who publishes this API and is it verified?

It is published by SharpAPI and listed as Verified on ApyHub.

What are the costs of using the two endpoints?

The submit endpoint costs 50 atoms per call and the job status check endpoint costs 1 atom per call, per the try-it-live pricing shown.

Advertise here

Featured products

  • SerpApi - Search API favicon
  • Screenshot Scout favicon
  • TalorData favicon
  • CoreClaw favicon

Show your product to thousands of developers

· 100k monthly pageviews
· 7k newsletter subscribers

Advertise your product