PagibleAI uses DeepL for page and reusable-content translation by default. DeepL API Free and API Pro use different endpoints, so choose the URL that matches your key.
Configure DeepL for PagibleAI
Choose a DeepL API plan
- Open the DeepL API plans.
- Choose API Free for limited monthly usage or API Pro for usage-based billing and cost controls.
- Finish the account setup in DeepL.
A DeepL Translator subscription does not include DeepL API access.
Get a DeepL API key
Open API Keys in your DeepL account and create a key for this site. Copy it to your deployment secret store. The DeepL authentication guide lists the current Free and Pro endpoints.
Keep the key out of CMS content, logs, browser code and source control.
Add the key to PagibleAI
The Free endpoint is the default. Set CMS_AI_TRANSLATE_URL only when you use an API Pro key:
DEEPL_API_KEY="..."
CMS_AI_TRANSLATE_API_KEY="${DEEPL_API_KEY}"
# DeepL API Pro only
# CMS_AI_TRANSLATE_URL="https://api.deepl.com"
Run the command below after changing the key or endpoint. Restart Octane, queue workers and other long-running PHP processes.
php artisan config:clear
Test DeepL
Translate a short draft page or reusable element into a language enabled in your CMS. The translated fields should appear in the draft editor. Check names, links and structured fields before saving.
Troubleshooting
Why does PagibleAI say “No API key”?
Map CMS_AI_TRANSLATE_API_KEY to DEEPL_API_KEY, clear the configuration cache and restart long-running PHP processes.
Why does DeepL return 403?
Check that the key is active and that the endpoint matches the plan. Free keys use api-free.deepl.com; Pro keys use https://api.deepl.com.
Why does DeepL return 456?
The account has reached its character or cost-control limit. Check usage and limits in DeepL before retrying.
What if the key was exposed?
Deactivate it, create a replacement, update the deployment secret, clear the configuration cache and restart workers.