What your organization gets
Submit from your own systems
Your CMS, product-information pipeline or marketing tool posts a document and its target markets. Every market becomes its own job, exactly as if your team had submitted it in the Transcreate Studio.
Know the moment a file is ready
Signed webhooks tell your system when a job is completed, when one could not be finished, and when a professional human review is delivered — no polling required.
Ready-to-publish files back
Download your own file rebuilt in the target language — Word, PowerPoint, Excel, PDF, subtitles, string files, HTML e-mails — or another format offered for the job.
Your AI assistant can use it
Transcreate AI is also an MCP server. In Claude Code or Claude Desktop, someone on your team can ask the assistant to transcreate a document, and it submits, follows and fetches the job for them.
The same quality pipeline
API jobs run through the same pipeline as the Studio: your brand glossary and translation memory, an AI critic that scores every passage on MQM-aligned dimensions, and professional human review when you order it.
One balance, no API surcharge
API jobs draw from the same Word Bank as the Studio, reserved and refunded on the same terms. There is no separate price for using the API.
How an integration works
- We switch the API on for your organization. It is off by default for every organization; write to hello@transcreateai.com and we enable it.
- An admin of your organization creates a key in Settings › Organization › API. The key is shown once; only a one-way hash of it is stored.
- Your system submits documents with
POST /v1/jobs, naming the target markets, audience and options — the same choices as in the Studio. - Your webhook endpoint is told when each job completes, and your system downloads the file with
GET /v1/jobs/{id}/result.
Jobs submitted through the API appear in the Studio beside everything else, so your team can review, comment, order a professional review or download them there too.
Billing
There is no separate API price. Each target market of a request is one job, and it draws its words from your organization's Word Bank at the same moment and on the same terms as a Studio submission. A job that fails, or is canceled within its window, gives its words back. A request for several markets reserves each one separately, so one market refused for lack of words does not stop the others.
Security and your data
- Keys belong to your organization, are created only by its admins, and can be revoked at any time; revocation takes effect on the next request. Only a SHA-256 hash of each key is stored, so nobody at Transcreate can read one back.
- Every request is scoped to your organization. A key reads and submits only your organization's jobs.
- Webhooks are signed with HMAC-SHA256 under a secret of each endpoint's own, with a timestamp so an old delivery cannot be replayed. Secrets can be rotated, with the previous one kept valid for 24 hours.
- Webhooks carry no content. A delivery names the job, its state, its market, timestamps and links — never your text and never a file name. Your system fetches the details with its key.
- Webhook addresses must be HTTPS and public. Private, loopback, link-local and cloud-metadata addresses are refused when an endpoint is registered and again before every delivery, and redirects are not followed.
- Your activity log records it. Key creation and revocation, and every job submitted through the API, appear in your organization's activity log with the key that did it.
- The same retention as the Studio. API and MCP requests are stored, kept and purged exactly like Studio work; nothing extra is kept because a request came through the API.
Technical reference
The essentials for your engineers. The complete reference — every field, every error code, signature-verification code in Python and Node — is sent with your first key.
Base URL and authentication
https://api.transcreateai.com/v1
Authorization: Bearer tai_live_…JSON responses; job submission is multipart/form-data. Keys stay on your servers — never in a browser, a mobile app or a repository.
Submit a document
curl -X POST https://api.transcreateai.com/v1/jobs \
-H "Authorization: Bearer $TRANSCREATE_API_KEY" \
-H "Idempotency-Key: order-81723" \
-F "file=@brochure.docx" \
-F "target_language=Spanish (Mexico)" \
-F "target_language=French (France)" \
-F "audience=Parents of young children"Endpoints
| Method | Path | What it does |
|---|---|---|
| POST | /v1/jobs | Submit one document (or text) for one or more target markets — up to 20 per request. |
| GET | /v1/jobs | List your organization's jobs, newest first, including those submitted in the Studio. |
| GET | /v1/jobs/{id} | One job's state: queued, running, finishing, completed, failed or canceled. |
| GET | /v1/jobs/{id}/result | Download the finished file, in its own format or another one offered for the job. |
- Formats: Word, PowerPoint, Excel and PDF; images (including HEIC and WebP); plain text, subtitles (.srt, WebVTT) and CSV; string files (JSON, YAML, .po, .strings, XLIFF); HTML e-mail templates; and older Office and OpenDocument files, which are converted on arrival.
- Options: audience, tier, translation mode (transcreation, translation or strict fidelity), a CSV column, a character limit, a job label and the market's quotation-mark style — the Studio's own choices.
- Retries are safe: send the same
Idempotency-Keywhen retrying a request and you get the first request's jobs back. Nothing is charged twice. - Errors are JSON with a stable
codeand a readablemessage; refusals from the job pipeline are the same ones the Studio shows.
Webhooks
| Event | When |
|---|---|
| job.completed | A job's file is ready to download. |
| job.failed | A job could not be finished; its words are refunded to the Word Bank. |
| review.delivered | A professional human review of a job was delivered. |
Transcreate-Signature: t=1790949598,v1=5257a869e7ecebed…
v1 = hex( HMAC-SHA256( secret, "{t}.{raw body}" ) )Answer with any 2xx within 10 seconds. A failed delivery is retried eight times over about 24 hours, and the delivery id stays the same on every retry, so duplicates are easy to ignore.
Limits
- Requests
- 60 per minute per key, across every endpoint
- Submissions
- 10 requests per minute per key
- Jobs started
- 60 per minute per organization, one per target market
- Markets per request
- 20
- Keys per organization
- 25 active
- Webhook endpoints
- 10 per organization
- File size
- Your organization’s upload limit — 25 MB by default, up to 100 MB on request
Over a limit, the API answers 429 with a Retry-After header in seconds, and nothing is started or charged.
For AI assistants: the MCP server
Transcreate AI is a remote MCP server (Model Context Protocol) at https://api.transcreateai.com/mcp, authenticated with the same API keys and the same limits. It gives an assistant five tools: submit a document, check a job, list jobs, fetch the finished file, and look up your brand glossary (read only).
claude mcp add --transport http transcreate https://api.transcreateai.com/mcp \
--header "Authorization: Bearer $TRANSCREATE_API_KEY"That is Claude Code; Claude Desktop connects through the mcp-remote bridge, and any client that speaks Streamable HTTP and can send a request header works the same way. Submitting through an assistant is billed like any submission, and the tool is marked so that the assistant asks before it spends words. What you share in the conversation, and what the tools return, is also seen by your assistant under its provider's terms — give it a key you can revoke on its own.
Ready to connect?
Write to hello@transcreateai.com and we will switch the API on for your organization and send your engineers the full reference.