Skip to content

Ship a glossary-aware translation API endpoint

Translate UI strings, help docs, and product descriptions while preserving brand terms, placeholders, and markdown syntax.

Copy the prompt and paste it into the AI assistant you already use.

Checklist for accurate localization endpoints

  1. 01

    Lock non-translatable tokens

    Add regex and prompt rules protecting template variables, URLs, and code snippets from alteration.

  2. 02

    Attach a domain glossary

    Store approved term pairs per target language so UI buttons stay consistent across releases.

  3. 03

    Pass tone and locale context

    Include target_locale and audience_register inputs rather than relying on bare language codes.

  4. 04

    Verify markup integrity

    Test payloads with nested HTML links and markdown headings to confirm zero broken tags.

Common questions

Why use an APIkit endpoint instead of raw translation APIs?

Raw translators frequently mangle placeholder variables or ignore product terminology. APIkit enforces your glossary, register, and markup rules on every call.

Can one endpoint translate into multiple locales at once?

Yes. Accept an array of target_locales in the request body and return a keyed JSON map with every translation in one round trip.

How are brand names kept untranslated?

You register protected terms in the endpoint configuration so the model leaves exact product and feature names verbatim.