Skip to content

DeepL API Legacy Authentication Deprecation #147

Closed

Description

@asfak-ur-rahman

Today, we received an email from DeepL regarding the deprecation of legacy authentication methods. As we rely on the deepl Python library for our translation services, maintaining uninterrupted access is critical for our operations.

1. Could you please confirm whether the changes mentioned will take effect on November 1, 2025?
2. Additionally, are there any actions required on our part to ensure continued service?

Image

Activity

  1. JanEbbing commented on Sep 12, 2025

    @JanEbbing
    Contributor

    All client libraries have always used the proper authentication method (via the Authorization header) and are thus not affected by this change.

    1. Could you please confirm whether the changes mentioned will take effect on November 1, 2025?

    Yes, I can confirm that

  2. asfak-ur-rahman commented on Sep 12, 2025

    @asfak-ur-rahman
    Author

    Thank you for confirming.
    Glad to know that no changes are needed on my end.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions