Skip to main content
GET
Retrieve detailed information about a specific translation order using its unique identifier. This endpoint provides comprehensive order details including status, documents, and financial information.

Authorizations

This endpoint requires API key authentication. Include your API key in the request header:
  • Header name: X-Api-Key
  • Header value: Your API key from the Ollang dashboard
  • Format: X-Api-Key: your-api-key-here
You can obtain your API key from your Ollang dashboard.

Path Parameters

string
required
The unique identifier of the order you want to retrieve. This should be a valid order ID that you have access to.

Response

string
Unique identifier of the order.
string
Creation date and time of the order (ISO 8601 format).
string
Name or title of the order.
string
Source language of the content, as a BCP-47 language tag from Supported Languages (e.g., ‘en’, ‘tr’, ‘fr’).
string
Target language for translation, as a BCP-47 language tag from Supported Languages (e.g., ‘en’, ‘tr’, ‘es-MX’).
string
Type of the order. Creatable values are cc, subtitle, document, aiDubbing, and studioDubbing — see Order Types. The platform may additionally return legacy or system-generated values such as proofreading, other, or revision on orders that were not created through Create Order.
string
Current status of the order. Possible values: pending, ongoing, completed, revision, review, waitingForCC, waitingForSubtitle, waitingForApprove, delayed. Internal delivery and QC stages (delivered, qualityCheck, readyToSent, qcPending, qcDelivered) are reported as ongoing; review means the order is paused at a review gate. See Order Statuses.
number
Rate applied to the order for pricing calculation.
string
Associated project identifier that this order belongs to.
number
Service level for the order. Level 0 means full AI generated and Level 1 is Human Review added version.
string
Folder identifier where the order files are organized and stored.
string
URL to download the VTT subtitle file associated with the order (if available).
string
URL to download the order’s subtitles as an SRT file. It is built from the same subtitles as vttUrl, including completed reviews and revisions. Empty string when the order has no subtitles.
array
Array of documents associated with the order.
object
Download URLs of the order’s deliverables, picked from orderDocs so you don’t have to match document types yourself. Each named URL is null until that file exists for the order, and outputs lists every delivered file. See Downloading deliverables.
object
Financial details related to the order.
object
Quality check evaluation for this order, if available. This field is present when a QC evaluation has been run on the order.
array
Delivery milestones recorded for this order, oldest first. Use this to track an order’s delivery history programmatically — when the AI output became available, when a translator delivered their work, and when the order was delivered to you.Returns an empty array for orders that have not reached a milestone yet, and for orders created before delivery-event tracking was introduced (the log is not backfilled). The same event type can appear more than once — for example an LSP re-delivery, or an order that was rerun.

Downloading deliverables

For a subtitle and AI dubbing workflow, these fields give you each file without opening the dashboard: deliveryFiles.outputs lists every delivered file with its type, so you can download files that have no named field, such as the final visual translation video with burned-in subtitles (created_final_visual_translation_embedded_video) or a translated document. To get the dubbed video with subtitles burned in, call Request Subtitle Embedding on the AI dubbing order. Dubbing orders always burn the subtitles onto their dubbed video, so no extra parameter is needed. Rendering is asynchronous, so poll this endpoint until deliveryFiles.videoWithBurnedInSubtitlesUrl is set. If the order already had a burned-in video, the field keeps pointing to it until the new one has finished. Compare the updatedAt of the created_subtitle_embedded_video entry in orderDocs with the time of your request to tell them apart. All URLs are presigned and expire. Download the files soon after you read the order, and request the order again if a link has expired.
Python