# DeepL Http post problem - depracated API effective March 14th

**URL:** <https://community.homey.app/t/deepl-http-post-problem-depracated-api-effective-march-14th/127754>\
**Category:** Questions & Help\
**Created:** [January 14, 2025, 9:38pm UTC](https://community.homey.app/t/deepl-http-post-problem-depracated-api-effective-march-14th/127754 "2025-01-14T21:38:56Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![naehle](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/naehle/32/79073_2.png) [@naehle](https://community.homey.app/u/naehle)\
**Post date:** [January 14, 2025, 9:38pm UTC](https://community.homey.app/t/deepl-http-post-problem-depracated-api-effective-march-14th/127754/1 "2025-01-14T21:38:56Z")

</div>

Hi,  
currently I am using a http get request to the free deepl api to translate the weather forecast from open weather.  
Now, deepl is depressing get request and requires post requests effective March 14th:

> **[March 2025: Deprecating GET requests to /translate and authenticating with...](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/march-2025-deprecating-get-requests-to-translate-and-authenticating-with-auth_key)**

My attempt causes a 403 forbidden error:

 ![Bildschirmfoto 2025-01-14 um 22.31.27](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/f/1/f1fc275d1007d6ef18275298090792ece9aeca5a.jpeg)

Any help would be greatly appreciated.

Regards

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [January 14, 2025, 10:46pm UTC](https://community.homey.app/t/deepl-http-post-problem-depracated-api-effective-march-14th/127754/2 "2025-01-14T22:46:02Z")

</div>

Your host/url is different from the example @ [https://developers.deepl.com/docs/resources/breaking-changes-change-notices/march-2025-deprecating-get-requests-to-translate-and-authenticating-with-auth\_key](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/march-2025-deprecating-get-requests-to-translate-and-authenticating-with-auth_key) :

```auto
POST /v2/translate HTTP/2 
Host: api.deepl.com
Authorization: DeepL-Auth-Key [yourAuthKey]
User-Agent: YourApp/1.2.3
Content-Length: 45
Content-Type: application/json
{"text":["Hello, world!"],"target_lang":"DE"}

```

Or, POST requests only get activated as per March 14th?

---

<div class="post-metadata">

**Author:** ![naehle](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/naehle/32/79073_2.png) [@naehle](https://community.homey.app/u/naehle)\
**Post date:** [January 15, 2025, 7:10am UTC](https://community.homey.app/t/deepl-http-post-problem-depracated-api-effective-march-14th/127754/3 "2025-01-15T07:10:12Z")

</div>

well, if you follow this link [https://developers.deepl.com/docs/api-reference/translate](https://developers.deepl.com/docs/api-reference/translate) on the webpage referenced above you are redirected to a page containing more information on syntax etc. and also the friendly reminder to use [api-free.deepl.com](http://api-free.deepl.com) in case you are not a paying subscriber.

As for the date, the way I understand the information is that the GET will become deprecated on March 14th, but POST is already possible.

So, my syntax / usage appears to be correct to you?

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [January 16, 2025, 1:17am UTC](https://community.homey.app/t/deepl-http-post-problem-depracated-api-effective-march-14th/127754/4 "2025-01-16T01:17:33Z")

</div>

Ah, missed that part.  
To me, your flowcard appears to be OK, it looks like the card below;  
Make sure the _ **line break** _ between your auth-key and _Content-type_ should be created with the **Shift+Enter** key combi

 ![1000000401](https://us1.discourse-cdn.com/flex025/uploads/athom/original/3X/3/4/34a4184b56677216edfa3eb011c55134ef39d8b9.jpeg)

Unfortunately I can’t test myself, since no creditcards present here.

But, 403 Forbidden means your key is incorrect, or is it possible you’ve exceeded the max API calls? (500.000 character limit / month)  
Note: The incorrect (transmitted) key might be a result of a unallowed trailing linebreak

---

<div class="post-metadata">

**Author:** ![naehle](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/naehle/32/79073_2.png) [@naehle](https://community.homey.app/u/naehle)\
**Post date:** [January 16, 2025, 8:39pm UTC](https://community.homey.app/t/deepl-http-post-problem-depracated-api-effective-march-14th/127754/5 "2025-01-16T20:39:39Z")

</div>

solved…  
it´s crazy… and quite logical at the same time:

Authorization: DeepL-Auth-Key [yourAuthKey]

Really means “Authorization: DeepL-Auth-Key [yourAuthKey]”, i.e. not everything after “”:" is replaced with the Auth Key, but only [yourAuthKey]…

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [January 17, 2025, 7:08am UTC](https://community.homey.app/t/deepl-http-post-problem-depracated-api-effective-march-14th/127754/6 "2025-01-17T07:08:57Z")

</div>

Oh that’s odd! Good find.  
The logical thing (to me) would be to only enter the auth key (assuming the other text is for explanation purposes only. But, “_thy should not assume_” 😜 )

But when you look close at the example, it really shows were to put the auth key exactly