Translate an email
A support inbox that receives tickets in a dozen languages usually forces a small team to either hire native speakers for each one or make customers wait for whoever happens to read that language. The Email Translation endpoint translates the incoming message and the outgoing reply while preserving tone, so a support agent can answer a French customer in fluent French without speaking a word of it.
Run it online
Run this on our servers with your account. Free tools run in your browser; this one bills your KIT balance per the price above.
Who actually hits this wall
Support teams rarely get to choose which languages their customers write in, and hiring a native speaker for every market a product sells into is not realistic for most companies below a certain size. What usually happens instead is a slow, apologetic reply routed through whoever on the team half-remembers high school Spanish, or a multi-day delay while a message waits for the one bilingual agent to log in. This endpoint exists for that exact gap: teams who need accurate, natural-sounding translation of both the incoming ticket and the agent's reply, not a rough gist.
What it does with tone, not just words
Support email carries register that matters: a frustrated customer's message reads differently than a routine password reset request, and a reply needs to match that register in the target language, not sound stiffly formal when the original was casual, or vice versa. Submit the email body along with the target locale, and the task translates while keeping the tone consistent with the source, since a technically accurate translation that reads cold undermines the whole point of replying personally.
How the request and result work
The call runs asynchronously and returns a task_id right away since translation with tone-matching is not instant; when it completes, the translated email arrives via the signed webhook, the recommended path for a live support queue, or a signed link valid for 24 hours if you are pulling results manually. Nothing about the flow requires a human to sit and wait on a spinning cursor.
Fitting it into a support workflow
The natural setup wires an incoming ticket in an unfamiliar language to this endpoint first, so the agent reads it in their own language, drafts a reply in their own language, and sends the reply back through the endpoint before it goes out to the customer. Helpdesk software has offered auto-translate widgets for years, but a dedicated API lets a team route only the languages that actually need it, log every translation for quality review, and keep the workflow inside their own tooling instead of a bolted-on browser plugin.
Where a person still needs to look
Legal or compliance-sensitive replies, refund policy language, and anything a customer might screenshot and escalate deserve a bilingual reviewer's eyes before sending, the same caution any company would apply to a human translator's first draft. What this endpoint removes is the wait: a ticket that used to sit for two days waiting on the one Portuguese-speaking agent can get an accurate draft translation in minutes.
What you can do with it
Multilingual helpdesk without hiring per language
A five-person support team fields tickets in eight languages by translating each incoming email on arrival and translating replies before sending, without hiring a native speaker for every market.
Tone-sensitive escalations
An agent handling a frustrated customer's complaint gets a translation that preserves the urgency and tone of the original, instead of a flattened, overly formal rendering.
After-hours coverage
A support queue that receives tickets overnight in a language no on-shift agent speaks routes them through translation automatically instead of waiting until the right agent logs on.
Quality logging for a growing team
A company scaling its support org keeps every translated ticket and reply logged for review, building a record it can audit as the multilingual queue grows.
FAQ
Does it preserve the tone of the original email?
Yes, the endpoint translates while matching the register of the source message, so a frustrated or casual email does not come out reading stiffly formal, and vice versa.
Is the email translation API free?
There's no free tier — free tiers get abused and slow everyone down. Access runs on a prepaid ForHosting KIT balance: top up from $10.00 (it never expires) and each request is charged at its published price, so a call with no balance returns HTTP 402. No subscription, no tokens, no invented credits, and a failed task is never charged.
Can I use it for both incoming tickets and outgoing replies?
Yes, the same endpoint handles either direction; submit the ticket to read it in your language or submit your reply to send it in the customer's language.
How fast do I get the translated email back?
It runs asynchronously and returns a task_id immediately; the translated result typically arrives within moments via webhook, which is the recommended delivery method for a live support queue, or a signed link valid 24 hours.
Is it accurate enough for sensitive or legal replies?
It produces an accurate first draft, but any reply involving legal, compliance or refund language should get a bilingual reviewer's check before sending, the same standard applied to any first-draft translation.
Can I bulk-process a backlog of tickets?
Yes, submit multiple ticket translations in parallel and let each task_id resolve independently rather than waiting on one at a time.
What happens if the translation fails?
The system retries automatically up to three times; if it still fails you receive a clear error and are not charged for the attempt.
Are my customers' emails stored or used to train models?
No. Email content is processed only to produce your translation and deleted after the retention period; it is never used for training.
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, and soon from our app, email and Telegram.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/translate/email \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"input":"…"}'const res = await fetch("https://api.kit.forhosting.com/translate/email", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"input": "…"
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/translate/email",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"input": "…"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/translate/email", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"input":"…"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"input":"…"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/translate/email", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"input": "…"
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "translate.email",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Limits
max_tokens | 20000 |
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
422 | task_failed | The task failed after 3 retries. You are never charged for it. |