Pending changes to DeepL API for Nov 1 2025

[edporras]

Hello,

We received an email from Deepl concerning a change to API request authentication:

Effective November 1 2025, all API requests must be authenticated by sending your API key in an Authorization HTTP header with the format:
Authorization: DeepL-Auth-Key [yourAuthKey].

What this means for you:
 
If you are using an officially supported DeepL client library, you are not affected by this change and no action is required.
 
If you are using a custom-built application or a third-party plugin, you must update your code to use the new header-based authentication method before the deadline. Requests using the deprecated methods after this date will fail.
 
For more detailed information and technical guidance, please visit our documentation page:
[https://developers.deepl.com/docs/resources/breaking-changes-change-notices/november-2025-deprecation-of-legacy-auth-methods](https://developers.deepl.com/docs/resources/breaking-changes-change-notices/november-2025-deprecation-of-legacy-auth-methods)

I wanted to check if this will require an update to the plugin or not?

Thank you very much and thank you for this wonderful plugin.

[layaxx]

Hi @edporras ,
thank you for your question.

We currently use "deepl-node": "^1.13.1" for all interactions with the Deepl API, and according to the relevant Deepl docs no update or further action should be needed.