DeepL API
GET /v2/languages endpoint removal
Deprecated, no dateSubscribe to DeepL APIShare
DeepL has deprecated the GET /v2/languages endpoint without announcing a shutdown date. Calls made to this route are marked for removal and will eventually fail. DeepL API notes that the endpoint is now deprecated alongside related language pair endpoints.
Calls it hits
GET /v2/languages
What to use instead of these calls
Migrate your calls to /v3/languages.
In DeepL API's words
/v2/languages and /v2/glossary-language-pairs are now deprecated.
Facts
Questions
When does this change take effect?
DeepL API deprecated GET /v2/languages without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: DeepL API 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 DeepL API 4
-
GET /v2/translateEndpoint removal Stopped working -
body parameter auth_keyParameter removal Stopped working -
query parameter auth_keyParameter removal Stopped working -
No date
GET /v2/glossary-language-pairsEndpoint 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.