Steve Rawcliffe Thilo Pawelka Ismael Garay 

We have been discussing a few things with the DeepL team and I wanted to make sure you understood that this feature will not be available to you if you only have a Pro account?

It will only be available to users with a "DeepL API for Business" subscription.  This is because of what DeepL support, not because of anything we are restricting.

To quote the information we were provided with:

"However, in case of additional development to your plugin, it should be noted that customers with a DeepL Pro Advanced or Ultimate subscription (the prerequisites for CAT Tool integration) are not allowed to create the glossaries themselves via direct API request.
Direct access to our API by customers who do not have a DeepL API subscription counts as a violation of our Terms and Conditions and may result in a corresponding suspension for these customers."

So this means you have to have a DeepL API subscription of which they offer three types:

• DeepL API Free
• DeepL API Pro
• DeepL API for Business

Of these three only one includes CAT tool integration and that's "DeepL API for Business".

We are currently investigation with DeepL how we are able determine the style of subscription a user has as this is not clear.  But this is likely to be news for some users, possibly like you, who have a Pro subscription and believed this meant you can work with glossaries.

You should also be aware that there are glossaries, and there are glossaries!  The glossaries you create using the API are not the same as the glossaries you create manually.  So you will not be able to use the ones you created in your account as they cannot be accessed via the API... and vice versa.  This means a lot of synching between the two if you wish to keep them in synch... something you will have to do manually.

Also, the DeepL API does not support an ability to change a glossary.  So if you need to make changes you would have to delete the existing one and recreate a new one.

All in all possibly not a particularly attractive option.  I would be very interested to learn your view on this information if you were not aware of it already?

Thank you for your detailed answer and the update on the state of affairs.
It is of course annoying that there is no easy way to use glossaries via the DeepL Pro subscription, but DeepL will have its reasons.
Since last year we have been using a third party plugin (Custom MT) to integrate the glossaries and are very happy with it.

Thilo Pawelka 

Thilo Pawelka said:

Since last year we have been using a third party plugin (Custom MT) to integrate the glossaries and are very happy with it.

I'm very glad to hear it.  Do you need to have a DeepL API for Business subscription for this or is everything handled through CustomMT?

No, you don't need a DeepL API for Business subscription to use the DeepL glossary feature through CustomMT. You do need a subscription with CustomMT, but I think the DeepL glossary feature is included in the free basic package.

Thilo Pawelka 

Thilo Pawelka said:

I think the DeepL glossary feature is included in the free basic package.

There's a difference between the glossaries with the free package and the glossaries used in a CAT tool via the API.  The subscription plans separate then quite distinctly and they are not interchangeable.

Sorry, that was unclear: I meant the free basic subsciption package with CustomMT. You can have a free subscription with CustomMT an be able to use the DeepL glossary feature through their Trados plugin without the need of having any subscription with DeepL. At least to my understanding.

Just to clarify: the Custom.MT plugin supports glossaries for Deepl and it does not require a Deepl API subscription. A "Deepl Pro" account is sufficient. The user needs to enter the API key from Deepl once into the Deepl engine settings on the Custom.MT console before he can add glossaries.

Just to clarify: the Custom.MT plugin supports glossaries for Deepl and it does not require a Deepl API subscription. A "Deepl Pro" account is sufficient. The user needs to enter the API key from Deepl once into the Deepl engine settings on the Custom.MT console before he can add glossaries.

Sounds like that could be worth trying!

Walter Blaser 

Walter Blaser said:

Just to clarify

This does not clarify at all.  I have dropped an email to Custom.MT to understand what they are doing in the background to support this.  I think it's important to recognise that DeepL have been quite clear that you cannot use glossaries via the API without a DeepL API pro or Business subscription, and you cannot use a CAT tool integration with only a DeepL API Pro subscription so somewhere in this loop someone has to pay for the full subscription required.

It's not enough to just have a DeepL API Pro account.  If you use some other service to fill the gaps in the subscription and you pay them instead then that's probably fine as they may pay DeepL in some agreement they have with them; and if you also pay for an Advanced or Ultimate subscription then that may be fine (I have asked DeepL this question).  But please let's not muddy the waters here and confuse everyone because (financially and to avoid violation of their terms & conditions) a DeepL API Pro account is not sufficient without something else supporting the CAT tool integration.

I can confirm this: you can use DeepL glossaries via custom.mt if you have the DeepL Pro Advanced subscription; no need for any of the API subscriptions (which makes sense, as they're intended for developers). Works like a charm.

AFAIK this is the only way to access DeepL glossaries from Studio 2021. In Studio 2022, you can also access them via the DeepL plugin, which is probably the better option unless you're using custom.mt anyway.

Two things I discovered regarding custom.mt are:

• it's essential to confirm your e-mail address in custom.mt; if (like me) you didn't get a mail asking you to do that, contact their helpdesk and they'll sort it
• for me at least it was only possible to attach a glossary when I connected to the custom.mt console using Firefox, not Chrome, though that may be an oddity of my installation.