Deepl no auth web client API
Now the web client (no auth) api use an Websocket or Longpolling from "https://ita-free.www.deepl.com/v1/sessions?id=connectionToken" the token can be obtain from : https://ita-free.www.deepl.com/v1/sessions/negotiate?negotiateVersion=1 (post)
(for pro it's "ita-pro" instead of "ita-free" but i dont have pro)
the server and client mostly send messagePack data that contains Protobuf data
with this api we can : change between deepl classic and next-gen model set tone (formal and informal), even though it is “supposed” to be a pro feature. set glossaries
Have you tested that there will be no issues with frequent requests?
Have you tested that there will be no issues with frequent requests?
It works with a session (websocket) and they can limit a session, but we can simply recreate the session to get around that limit. (I've encountered a 429 error before, but it's probably when we create too many sessions quickly) (DeeplWrite also uses this API) (it uses SiganlR + MessagePack, and it sends Protobuf data)
if we use https://ita-pro.www.deepl.com instead of https://ita-free.www.deepl.com we might remove the limit (no need to recreate the session) but we need to have pro account