---
title: "Check Document Status"
method: POST
path: "/v2/document/{document_id}"
tags: ["TranslateDocuments"]
---

# Check Document Status

`POST /v2/document/{document_id}`

## Path parameters

- `document_id` string, required

## Request body

- DocumentKey
  - `document_key` string, required — The document encryption key that was sent to the client when the document was uploaded to the API.

## Response `200`

The document status request returns a JSON object containing the document ID that was used in the request as well as string indicating the current status of the translation process. While the translation is running, the estimated number of seconds remaining until the process is done is also included in the response.

- object
  - `document_id` string, required — A unique ID assigned to the uploaded document and the requested translation process. The same ID that was used when requesting the translation status.
  - `status` 'queued' | 'translating' | 'done' | 'error', required — A short description of the state the document translation process is currently in. Possible values are: * `queued` - the translation job is waiting in line to be processed * `translating` - the translation is currently ongoing * `done` - the translation is done and the translated document is ready for download * `error` - an irrecoverable error occurred while translating the document
  - `seconds_remaining` integer — Estimated number of seconds until the translation is done. This parameter is only included while `status` is `"translating"`.
  - `billed_characters` integer — The number of characters billed to your account. The characters will only be billed after a successful download request.
  - `error_message` string — A short description of the error, if available. Note that the content is subject to change. This parameter may be included if an error occurred during translation.

## Other responses

- `400` — Bad request. Please check error message and your parameters.
- `403` — Authorization failed. Please supply a valid `DeepL-Auth-Key` via the `Authorization` header. This error is also returned when the API key is scoped but does not include the scope required for this endpoint.
- `404` — The requested resource could not be found.
- `413` — The request size exceeds the limit.
- `429` — Too many requests. Please wait and resend your request.
- `456` — Quota exceeded. The character limit has been reached.
- `500` — Internal error.
- `504` — Resource currently unavailable. Try again later.
- `529` — Too many requests. Please wait and resend your request.

---

[API](https://skmtc.dev/deepl/apis/deepl-api-documentation.md) · [All operations](https://skmtc.dev/deepl/apis/deepl-api-documentation/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/deepl/deepl-api-documentation/revisions/3c422fcc9c54/schema)