Pro využití této funkce je nutné si vytvořit účet na stránce
https://www.deepl.com/pro-checkout/account?productId=1200&yearly=false&trial=false

Při tvorbě účtu je nutné ověřit fyzickou existenci zadáním čísla platební karty a ověřením přes 
bankovní aplikaci. 
V případě placené varianty pak probíhají platby přes tuto kartu.


Následně je potřeba zkopírovat autentizační klíč, který je nutno zapsat do přepínače ors.SFResourceTranslator_authKey řízeného objektu SFResourceTranslator.

Klíč se nachází po přihlášení na adrese
https://www.deepl.com/account/summary
A má formu řetězce znaků např.
df4385c2-33de-e423-4134-ca1f7b3ea8b7. 

Na stránce účtu máte přehled o aktuálním využití.
 {{ :orfertopen:sfresourcetranslator.png?nolink&400 |}}


Spefifikace Free licence

DeepL API Free

Conditions of your plan
Your subscription to DeepL API Free is completely free.
You can translate up to 500,000 characters per month.
You can upgrade to DeepL API Pro at any time.
Features of your plan
Access to DeepL REST API
DeepL translation quality

Specifikace API:

1  DeepL API

The DeepL API is accessible through a REST interface. Request parameters are used to pass information to the API, results are returned in a suitable representation (e.g. JSON). Request parameters must be encoded in accordance with the documentation provided under https://www.deepl.com/docs-api.html. Authentication is based on fixed keys, SSL handling transport security. The translate function provides the following functionality:

    Text - Text to be translated

        Only plain text encoded in accordance with the documentation is supported.

    Source language - Language of the text to be translated. 
    If this parameter is omitted, the API will make efforts to detect the language of the text.
    Currently, the following languages are supported:

        BG (Bulgarian)

        CS (Czech)

        DA (Danish)

        DE (German)

        EL (Greek)

        EN (English)

        ES (Spanish)

        ET (Estonian)

        FI (Finnish)

        FR (French)

        HU (Hungarian)

        ID (Indonesian)

        IT (Italian)

        JA (Japanese)

        LI (Lithuanian)

        LV (Latvian)

        NL (Dutch)

        PL (Polish)

        PT (Portuguese)

        RO (Romanian)

        RU (Russian)

        SK (Slovak)

        SL (Slovenian)

        SV (Swedish)

        TR (Turkish)

        ZH (simplified Chinese)

    Target language - The language into which you want to translate can be one of the following:

        BG (Bulgarian)

        CS (Czech)

        DA (Danish)

        DE (German)

        EL (Greek)

        EN-GB (British English)

        EN-US (American
        English)

        EN (English) (unspecified variant for backward compatibility; please select EN-GB or EN-US instead)

        ES (Spanish)

        ET (Estonian)

        FI (Finnish)

        FR (French)

        HU (Hungarian)

        ID (Indonesian)

        IT (Italian)

        JA (Japanese)

        LI (Lithuanian)

        LV (Latvian)

        NL (Dutch)

        PL (Polish)

        PT-PT (Portuguese) (all Portuguese varieties excluding Brazilian Portuguese) 

        PT-BR (Brazilian Portuguese)

        PT (Portuguese) (unspecified variant for backward compatibility; please select PT-PT or PT-BR instead)

        RO (Romanian)

        RU (Russian)

        SK (Slovak)

        SL (Slovenian)

        SV (Swedish)

        TR (Turkish)

        ZH (simplified Chinese)

The translate function returns the following representation of the processing result:

    Detected source language - The language which has been detected for the source text. 

    Text - The translated text.

The DeepL API is designed to translate at least 600 characters per minute and per Customer; exceeding use may be limited, and Customers may encounter a 429 “Too Many Requests” error message, as described in the documentation.

For document translations, a minimum of 50,000 characters per document is charged at each time.

Applications using the API should implement a mechanism to handle such responses accordingly and, if appropriate, to try again later. A mechanism increasing the delay for another request exponentially is recommended.