# DeepL integrations: text translation and documents

> Upload a document for translation, create a glossary and create a style rule list in DeepL. Connect DeepL to the rest of your AI stack with Tray.ai.

**Canonical page:** https://tray.ai/connectors/deepl-integrations/
**Categories:** AI
**Connects through:** HTTP Connector

## Overview

DeepL is a machine translation service that translates text and whole documents between dozens of languages, with glossaries and style rules to keep terminology consistent. Tray.ai connects to DeepL through the HTTP Connector, so your workflows can call the DeepL API alongside the rest of your stack.

## Use cases

### Text translation

Work with text translation in DeepL from any Tray.ai workflow. The DeepL API covers calls such as translate text and improve text.

- Translate text
- Improve text
- Correct text

### Documents

Read and create documents in DeepL from any Tray.ai workflow. The DeepL API covers calls such as upload a document for translation and check document status.

- Upload a document for translation
- Check document status
- Download a translated document

### Glossaries

Read, create, update, and delete glossaries in DeepL from any Tray.ai workflow. The DeepL API covers calls such as list glossaries and create a glossary.

- List glossaries
- Create a glossary
- Get a glossary

### Style rules

Read, create, and delete style rules in DeepL from any Tray.ai workflow. The DeepL API covers calls such as list style rule lists and create a style rule list.

- List style rule lists
- Create a style rule list
- Delete a style rule list

### Usage

Read usage in DeepL from any Tray.ai workflow. The DeepL API covers calls such as check usage and limits and get usage analytics.

- Check usage and limits
- Get usage analytics

## Challenges Tray.ai solves

### Keeping DeepL credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store DeepL credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the DeepL API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the DeepL API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to DeepL?

Yes. Tray.ai connects to DeepL through the HTTP Connector, which calls the DeepL API directly. Any call the DeepL API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with DeepL?

The DeepL API uses an API key in a request header. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated DeepL connector?

DeepL runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated DeepL connector from the DeepL API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/