![]()
api.deepl.com · ProductivitySubscribeShare
DeepL API breaking changes
The breaking changes DeepL API announced that Okapi tracks: 5 in all.
Do you run the DeepL API? Make sure your users call it right →
At a glance
- API host
api.deepl.com- Kind
- Productivity
- Versions with breaking changes
- v2 (3)
- Breaking changes tracked
- 2 breaking changes with no date yet and 3 already in effect
- Last updated
Deprecated, no date yet 2
-
No date
GET /v2/glossary-language-pairsEndpoint removal Deprecated, no date -
No date
GET /v2/languagesEndpoint removal Deprecated, no date
Already in effect 3
-
body parameter auth_keyParameter removal Stopped working -
query parameter auth_keyParameter removal Stopped working -
GET /v2/translateEndpoint removal Stopped working
Where Okapi reads it
- Changelog developers.deepl.com/docs/resources/roadmap-and-release-notes
- OpenAPI spec raw.githubusercontent.com/DeepLcom/openapi/main/openapi.yaml
- Announcement developers.deepl.com/docs/resources/breaking-changes-change-notices/march-2025-deprecating-get-requests-to-translate-and-authenticating-with-auth_key
- Announcement developers.deepl.com/docs/resources/breaking-changes-change-notices/november-2025-deprecation-of-legacy-auth-methods
Know before your API calls break.
Okapi finds the calls a breaking change hits in your code and opens the pull request that fixes them.
Add to GitHub