api-free.deepl.com
GET /v2/glossary-language-pairs endpoint removal
Deprecated, no date
The provider deprecated the GET /v2/glossary-language-pairs endpoint on May 18, 2026, without announcing a shutdown date. Calls to this endpoint will eventually fail once the removal takes effect. This change affects any integration querying language pairs through the v2 glossary path.
Calls it hits
GET /v2/glossary-language-pairs
What to use instead of these calls
Use GET /v3/languages with the glossary resource instead. Consult the Migrating from v2/languages guide for details on completing the transition.
In api-free.deepl.com's words
/v2/languages and /v2/glossary-language-pairs are now deprecated.
Facts
- API
- api-free.deepl.com
api-free.deepl.com - Kind
- Endpoint removal
- Announced
- May 18, 2026
- Takes effect
- No date given yet
- 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?
api-free.deepl.com deprecated GET /v2/glossary-language-pairs without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: api-free.deepl.com has not given a shutdown date yet.
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 -
query parameter auth_keyEndpoint removal Stopped working -
No date
GET /v2/languagesEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.