api-free.deepl.com
query parameter auth_key endpoint removal
Stopped working
On January 15, 2026, the query parameter auth_key will stop working for calls to api-free.deepl.com. The deadline for this deprecation has been extended to January 15th, 2026. Any requests passing credentials using the query parameter auth_key after that date will fail.
Calls it hits
query parameter auth_key
What to use instead of these calls
Send the key in the Authorization header instead, using Authorization: DeepL-Auth-Key [yourAuthKey].
In api-free.deepl.com's words
Update: The deadline for this deprecation has been extended to January 15th, 2026.
Facts
- API
- api-free.deepl.com
api-free.deepl.com - Kind
- Endpoint removal
- Takes effect
- January 15, 2026
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against api-free.deepl.com's own pages
Questions
When does this change take effect?
Calls to query parameter auth_key on api-free.deepl.com stopped working on January 15, 2026.
What happens to calls after January 15, 2026?
They have failed since January 15, 2026.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from api-free.deepl.com 4
-
GET /v2/translateEndpoint removal Stopped working -
body parameter auth_keyEndpoint removal Stopped working -
No date
GET /v2/glossary-language-pairsEndpoint removal Deprecated, no date -
No date
GET /v2/languagesEndpoint removal Deprecated, no date
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.