These endpoints are customer-scoped utility calls. They do not manage stored website translations or channel UI labels. Per-channel chat UI/message translations are covered by the Channels API through /api/ChannelTranslations and /api/Channels/{channelToken}/translations-by-token/{lang}.
POST /api/Translations/translate – Bearer JWTsourceText and targetLang. The current service uses gpt-4o-mini and returns the translated text as a plain string.GET /api/Translations/detect-language-ai – Bearer JWTcountry, state and city. country is required; state and city are optional context. The current service asks for an ISO 639-3 language code.POST /api/Translations/translate
Authorization: Bearer {token}
Content-Type: application/json
{
"sourceText": "Thank you for your message.",
"targetLang": "nld"
}sourceTexttargetLangnld, fra, deu or eng.countrystate, cityBedankt voor uw bericht.POST /api/Translations/translate200 OK with the translated text as a plain string, not a JSON object.GET /api/Translations/detect-language-ai200 OK with a language code string such as nld, fra or eng.Bearer JWT400404500POST /api/Translations/translate
Authorization: Bearer {token}
Content-Type: application/json
{
"sourceText": "Thank you for your message.",
"targetLang": "nld"
} Bedankt voor uw bericht. GET /api/Translations/detect-language-ai?country=Belgium&state=Flanders&city=Antwerp
Authorization: Bearer {token} nld GET /api/Translations/detect-language-ai uses location context to infer the most likely primary language. The API requires country; state and city add context.
sourceTexttargetLangnld, fra, deu or eng.countrystate, cityGET /api/Translations/detect-language-ai?country=Belgium&state=Flanders&city=Antwerp
Authorization: Bearer {token}nldsourceTexttargetLangnld, fra, deu or eng.countrystate, cityPOST /api/Translations/translate200 OK with the translated text as a plain string, not a JSON object.GET /api/Translations/detect-language-ai200 OK with a language code string such as nld, fra or eng.Bearer JWT400404500For stored per-channel UI/message translations such as chat titles, greetings, button text and escalation prompts, see the Channels API Reference. The current channel translation management routes are /api/ChannelTranslations, and public token-based retrieval uses /api/Channels/{channelToken}/translations-by-token/{lang}.
No. The Translations API translates an ad hoc plain text value or detects a likely language from location context. Stored chat UI/message translations are managed through the Channels API and /api/ChannelTranslations.
No public controller route currently exposes HTML translation. Use POST /api/Translations/translate for plain text and handle any HTML conversion in your integration.
The API loads the authenticated customer record and uses that customer's configured OpenAI API key. If no key is configured, the endpoint returns 400.
AnswerPal: AI-powered customer service solutions to elevate your support and communication effortlessly.
For all support, sales, and partnership inquiries, email us at info@answerpal.eu
AnswerPal
Bisschoppenhoflaan 380
2100 Antwerp
Belgium
+32.36416685
BE 0862.692.858