Skip to main content
Custom dictionaries are per-project pronunciation and replacement lists. Each entry maps a written word to the text or IPA the TTS pipeline should pronounce instead. Use them for brand names, product names, acronyms, and domain vocabulary that should sound consistent across requests. Changes are available to synthesis after the dictionary mutation finishes. Pass the dictionary’s projectId on GenerateOptions; omission loads no project dictionary. With projectId, omit dictionaryIds to apply all active project dictionaries or pass a list to select exact IDs. JavaScript streaming configs currently lack projectId, so dictionary-backed streaming requires the raw WebSocket protocol. For the full HTTP contract, field limits, master-key project_id rules, and error codes, see the Dictionaries API reference.

Create a Dictionary

Manage Dictionaries

Every dictionaries.* and dictionaries.entries.* method accepts an optional final { projectId } argument. It is required only for master-key callers acting on a specific project; with a normal API key, omit it.

Add and Manage Entries

Use replacement for normal spelling-based fixes. Use ipa when you need an exact phonetic pronunciation; IPA takes precedence over replacement.

Atomic Bulk Sync

replaceAll upserts every entry in one transaction and deletes entries currently in the dictionary whose word is not in the payload. Use it to sync from a CMS, PIM, or internal glossary.
replaceAll is intentionally destructive for omitted words. Only call it with the complete desired contents of that dictionary.

Generate With Dictionaries

Keep normalize enabled unless you have a specific reason to bypass text normalization.

Dictionary types


For automatic handling of numbers, dates, and spelled-out text, see Text Normalization.