Okapi Okapi

DeepL API GET /v2/glossary-language-pairs endpoint removal

Deprecated, no dateSubscribe to DeepL APIShare

DeepL has deprecated the GET /v2/glossary-language-pairs endpoint without a shutdown date. Calls made to this route are planned for removal and will eventually fail.


Calls it hits

  • GET /v2/glossary-language-pairs

What to use instead of these calls

Migrate your calls to /v3/languages instead.

In DeepL API's words

/v2/languages and /v2/glossary-language-pairs are now deprecated.

DeepL API, Changelog

Facts

API
DeepL API api.deepl.com
Kind
Endpoint removal
Takes effect
No date given yet
Calls after that day
Fail
Source
Changelog
Last updated
Verified
, against DeepL API's own pages

Questions

When does this change take effect?

DeepL API deprecated GET /v2/glossary-language-pairs 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

  1. GET /v2/translateEndpoint removal Stopped working
  2. body parameter auth_keyParameter removal Stopped working
  3. query parameter auth_keyParameter removal Stopped working
  4. 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.

Add to GitHub

Get notifications

Subscribe to DeepL API

Hear about each breaking change DeepL API announces, in your feed reader, calendar or Slack.

1What to follow

Provider
  • DeepL API

2Where to get it

/breaking-changes/feed.xml

Paste it into Feedly, Inoreader, NetNewsWire or any reader. New changes show up as they're announced.