For developers
Language, as an API. Every product.
Translate text, dub video, render voices, caption media — all via REST. Async with webhooks, streaming for low-latency TTS, per-key spend caps, multi-target batches. Bearer-key auth. Free tier ships with API access.
Six endpoints.
Every product.
The whole platform exposed as REST. Sync for short jobs, async with webhooks for everything else. Streaming for TTS where every millisecond is felt.
- POST/api/v1/translate
Translate text
Submit text or file, get back translation. Sync for short text, async with webhook for long jobs.
- POST/api/v1/tts/synth
Render a voice
Synchronous render with all options: voice, language, emotion, studio mode. Returns audio URL.
- POST/api/v1/tts/synth/stream
Streaming TTS
Chunked audio stream; playback starts at first phrase. Sub-second TTFB on common voices.
- POST/api/v1/dub
Dub a video
Submit URL or upload, pick target language and voice mode. Async; webhook fires when ready.
- POST/api/v1/subtitles
Caption a video
Subtitle generation with optional translation. SRT, VTT, TXT, bilingual SRT in response.
- GET/api/v1/usage
Usage & balance
Real-time credit balance, monthly spend, per-product breakdown for billing and budgeting.
Full reference, parameters and response shapes at /docs/api.
Built for production integrations.
- 01
Bearer-key auth
Authorisation: Bearer <key>. Per-key monthly spend caps. Per-key audit trail. Rotate or revoke without affecting the rest of your integration.
- 02
Webhooks with HMAC
POST callbacks on every terminal event. HMAC-SHA-256 signatures, replay protection, idempotency keys. Retry on receiver failure with exponential backoff.
- 03
Streaming TTS
Sub-second TTFB on the cast voices. Built for conversational agents that can't wait for a buffered render to complete.
- 04
Multi-target batches
Submit once, fan out to N target languages. Per-child progress, per-child download, single batch.completed event when the last child lands.
- 05
Idempotency keys
Pass Idempotency-Key on any POST and the platform deduplicates against the last 24 hours of requests. Safe for retry-from-edge scenarios.
- 06
Sandbox + production
Test keys spend test credits against the same API surface. Promote to production keys with one click; same code path, no behavior differences.
Translate. In four lines.
curl https://traxlate.com/api/v1/translate \
-H "Authorization: Bearer $TRAXLATE_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"Hello, world.","target":"ja"}'Python and Node snippets, batch examples, file-upload flows and webhook verification all in /docs/api.
Developer, answered.
Real questions from buyers, real answers. If something isn't covered here, the full FAQ lives at /faq and you can always open a ticket.
Which plans include API access?
+Every plan. The Free tier includes API access against your signup credits — test the integration before committing to a paid plan. Pro and Business get bigger monthly allocations and better overflow rates.
Sync or async?
+Sync for short text translation and short voice renders (under ~500 chars / under ~30 sec). Async for everything else — file uploads, dubs, long captions, long renders. Async returns a job_id + poll_url, and you can configure a webhook URL per API key to skip polling entirely.
What about rate limits?
+Generous defaults; per-key configurable. Enterprise plans get dedicated capacity. The /api/v1/usage endpoint exposes your current rate-limit headroom alongside credit balance.
Can I set per-key spend caps?
+Yes. Each API key has an optional monthly credit spend cap. Once hit, the API returns 402 until the following month. Prevents runaway costs from bugs or traffic spikes in your integration.
How do I handle large file uploads?
+POST a multipart upload up to 10 GB. The API returns immediately with job_id and poll_url; the file is processed in the background and the webhook fires when done. Resumable uploads are on the roadmap for >10 GB media.
What about webhook signing?
+Every webhook POST includes an X-Traxlate-Signature header — HMAC-SHA-256 over the body using your webhook secret. Verify before processing. Replay protection via X-Traxlate-Timestamp (reject events older than 5 minutes).
How do batches work?
+POST /api/v1/translate (or /dub, /subtitles) with targets: [...] returns a batch_id + child IDs. Each child reports independent progress. A single batch.completed webhook fires when the last child reaches a terminal state. Per-child success/failure surfaces in the aggregate payload.
Where are the docs?
+Full reference at /docs/api. Quickstart code in cURL, Python and Node. Webhooks chapter with verification snippets. Open the integration guide before you write a line of code.