DeepL API
GET /v2/translate endpoint removal
Stopped workingSubscribe to DeepL APIShare
Calls to GET /v2/translate on DeepL API stopped working on March 14, 2025.
Calls it hits
GET /v2/translate
What to use instead of these calls
Send POST /v2/translate with the text and target_lang in the request body, and include the key in an Authorization: DeepL-Auth-Key header.
In DeepL API's words
You will no longer be able to send GET requests or query parameters to the /translate endpoint. Going forward, /translate will accept only POST requests with data included in the request body.
Facts
- API
- DeepL API
api.deepl.com - Kind
- Endpoint removal
- Takes effect
- March 14, 2025
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against DeepL API's own pages
Questions
When does this change take effect?
Calls to GET /v2/translate on DeepL API stopped working on March 14, 2025.
What happens to calls after March 14, 2025?
They have failed since March 14, 2025.
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
-
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 -
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.