Here’s what we recommend reviewing to get your DeepL API application ready for production.
The fact that our pre-production checklist is published in the “Getting Started” section of the documentation is not a mistake!
We believe it’s useful information to have as you start exploring our product and thinking through your use case.
/translate
endpoint), use form-encoded (Content-Type: application/x-www-form-urlencoded
) or JSON-encoded (Content-Type: application/json
) request bodies.
Content-Type: multipart/form-data
; this content type should not be used for text translation.context
parameter. Learn more about working with context here.Here’s what we recommend reviewing to get your DeepL API application ready for production.
The fact that our pre-production checklist is published in the “Getting Started” section of the documentation is not a mistake!
We believe it’s useful information to have as you start exploring our product and thinking through your use case.
/translate
endpoint), use form-encoded (Content-Type: application/x-www-form-urlencoded
) or JSON-encoded (Content-Type: application/json
) request bodies.
Content-Type: multipart/form-data
; this content type should not be used for text translation.context
parameter. Learn more about working with context here.