DeepL Style Profiles on October 20, 2026: one style_profile_id replaces separate glossary, style and memory parameters

What you get

On October 20, 2026 DeepL released Style Profiles. A style profile groups your glossaries, style rule lists and translation memories under one ID. You pass style_profile_id to /v2/translate or /v2/document instead of listing each customization parameter. You can update the profile when the bundle changes without changing your integration.

DeepL applies only the parts that fit each request: glossaries for the language pair, the style rule list for the target language, and the translation memory for the source language. Profiles are managed through new endpoints under /v3/style_profiles.

A profile cannot be combined in the same request with glossary_id, glossary_ids, style_id, translation_memory_id, translation_memory_threshold or custom_instructions.

Prerequisites

• A DeepL API key in DEEPL_AUTH_KEY
• Existing glossaries, style rule lists or translation memories to bundle

Steps

1. Create a style profile with the /v3/style_profiles endpoints, following the style profiles guide linked from the release notes.
2. Add the glossaries, style rule list and translation memory you already use.
3. In your translate calls, send style_profile_id and remove the individual customization parameters listed above.

Test it

Translate one sentence that contains a glossary term, using only style_profile_id, and check the term is translated as your glossary says.

Not confirmed

• Which API plans include style profiles.
• Any limit on profiles per account or items per profile.
• Whether there is any extra charge.