Translation Settings

Connect your own DeepL API key and configure the translation engine

Default Engine (Without Your Own Key)

Without your own API key, meinGPT uses Google Cloud Translate for text translations and DeepL for file translations by default — see Engine, Hosting, and Data Protection for details.

Use Your Own DeepL Key (BYOK)

With the Bring Your Own Key (BYOK) feature you can store the API key from your own DeepL account. All translations — both text and documents — will then run through your DeepL account.

When is this useful?

  • Cost control — Billing goes directly through DeepL, not through meinGPT credits
  • Higher quotas — You use the limits and quota of your own DeepL plan
  • Compliance — Your organization manages the contractual relationship with DeepL directly

Prerequisites

  • A DeepL API Pro account (free DeepL API keys do not support glossaries)
  • The API key must have glossary management permissions
  • You need the Workspace Admin role in meinGPT

Setting up your key

Open settings

Navigate to Settings → Sidebar. In the "AI apps in the sidebar" section, click Settings next to Translator.

Enter your DeepL API key

Enter your DeepL API key in the input field and click Save.

Wait for validation

The key is automatically verified:

  • Format validation
  • Connection test with the DeepL API
  • Glossary permission check

On success, the key is encrypted and stored. It is displayed in masked form (e.g., ****ab12).

What changes

When BYOK is active, translations are no longer billed through meinGPT credits but directly through your DeepL account.

No API access

BYOK only changes how translations are billed within the meinGPT platform - not how you reach them. There is no dedicated API endpoint for text or file translation, and the Translator can't be triggered as a tool through the Completions API, the Assistants API, or the Workflows API. Translation only runs through the Translator interface in the platform - with or without your own DeepL key.

Updating or removing the key

  • Update: Click Update, enter the new key, and save. The old key is overwritten.
  • Remove: Click Delete and confirm the dialog. Translation switches back to platform billing via meinGPT credits. Glossaries are automatically migrated back.

Troubleshooting

Invalid API key

Make sure you copied the complete key. DeepL API keys use a UUID format (e.g., a1b2c3d4-...) or a 32-character hex format, optionally with a :fx suffix for free accounts.

Missing glossary permissions

Your DeepL plan must support glossaries. Free DeepL API keys do not offer this feature. Check your plan in the DeepL account settings.

Translations fail after key change

After a key change, glossaries are automatically re-synced on the next translation. If the error persists, verify that the new key is valid and has sufficient quota.

Technical Deep Dive

Was this page helpful?