I tried enpoints directly via browser.
The 403 is definetly coming from DeepL API v2.
v1 is working just fine.
https://api.deepl.com/v1/usage?auth_key=ourAuthKey -> {“document_count”:0,”document_limit”:20}
https://api.deepl.com/v2/usage?auth_key=ourAuthKey -> 403
Is your plugin using API v1 or v2?
I found this: https://www.deepl.com/docs-api/accessing-the-api/api-versions/
Version 2 (v2) of the DeepL API is not compatible with CAT tools and is not included in DeepL plans for CAT tool users.
Hi,
this is the log for the usage:
a:7:{s:4:”date”;s:19:”10/08/2020 11:54:06″;s:5:”class”;s:13:”DeepLApiUsage”;s:6:”uniqid”;b:0;s:4:”type”;s:5:”fresh”;s:4:”mode”;s:3:”GET”;s:14:”response_error”;i:403;s:8:”response”;a:2:{s:4:”code”;i:403;s:7:”message”;s:9:”Forbidden”;}}
It shows nothing under “Usage”.
Could it be that the 403 is a response from our server? Not from the API?
Maybe some server setting blocks the communication.
