Skip to content

DEVELOPER DOCUMENTATION

Your first translation request starts here.

Follow a clear path from creating a key to handling results in your product.

Quick start

Use a server-side API key to send JSON requests over HTTPS.

  1. 01

    Get a key

    Create an API key in the console.

  2. 02

    Submit text

    Set text and target_lang.

  3. 03

    Inspect the result

    Read the translation and track the request.

cURL
curl -X POST https://api.deeplvip.com/api/v1/translate \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text":"Hello, world!","target_lang":"zh-Hans"}'

Replace YOUR_API_KEY with your key. Keep it out of browser code and public repositories.

API endpoints

Translation and operational endpoints, with clear responsibilities.

POST/api/v1/translate

Submit one text and receive a translation, engine and request timing.

GET/api/v1/engines

Inspect registered engines and current availability.

GET/health

Health check for your deployment and load balancer.

GET/metrics

Prometheus metrics for usage, latency and service health.

Languages and response information

Use language codes supported by the selected engine, such as zh-Hans, en-US, ja and de. The optional engine parameter selects an engine; otherwise the default is used.

translation
Translated content
engine
Engine used for the request
characters
Source character usage
timing
Request timing information

Build error handling into the integration

4xx

Check credentials, request fields and language codes before resubmitting.

429

Reduce concurrency and use bounded exponential backoff. Respect Retry-After when provided.

503

Retry later or fall back as appropriate, with a strict retry limit.

Log request_id, status and timing while keeping credentials out of logs. See the FAQ for engine availability.

Read the FAQ