8 translator tutorials
Each article is one capability. It lists the request fields, a full call, and the success body. The API reference stays at /docs.
- 01Translate one stringUse it for a title, a message, or any single string that is not HTML.
- 02Translate a listUse it when you already have many short strings, such as UI labels, and want one round trip.
- 03Translate JSONUse it for a product record, a message object, or any JSON document whose keys must stay put.
- 04Translate HTMLUse it for a fragment or a document where tags, attributes, and selected subtrees must survive.
- 05Detect languageUse it before you choose a from code, or when you only need the language of a string.
- 06Choose a qualitySet it when a call must stay on one grade, or when you want an llm-first answer. Leave it unset for the fastest answer.
- 07Adult contextSend adult when the source is adult material. Omit context, or send general, for everything else.
- 08Glossary and protected wordsUse a glossary for product names that must become a chosen translation, and do_not_translate for codes, brands, or words that must stay byte-for-byte.