- Uploading Files
- Creating a Job
- Monitoring Job Status
- Downloading Translated Jobs
- Archiving Downloaded Jobs
- API Key - All requests throught the LILT API use the API Key to authenticate.
- File to Translate - We recommend a simple text file (txt) for a first attempt.
- Memory ID - A LILT Data Source’s
memoryId
to use with the translation - Create one here!
Submitting a New LILT Job
A LILT Job encapsulates the various files that you want to translate. A Job is usually made up of multiple Projects. A Project is a grouping of Documents to be translated for an individual language pair (en->de - English to German). The LILT app has a useful wizard for creating Jobs that breaks all of these concepts down into a single package. In the next section you will learn how to create your first LILT Job. If you are curious about how these objects fit together, feel free to check out the API Reference:Uploading Files
The first step is to upload some files. For this example, a text (txt) file will be used as it is one of the simplest file types supported for verified translation. See the API docs for more file upload options.TipUpload all of the files first before creating a Job with them.
Creating a Job
To create a Job you need at least one Data Source for the language you want to translate into. We will use the correspondingmemoryId
and the target language from that memory to specify a Language Pair, which can then be linked to the relevant Job.
For now, let’s create a Job for a single File and a single Language Pair. The request to create a Job will look like this. See the API docs for more info.
Monitoring the Job Status
To determine which translaions are ready for download query for jobs whereisDelivered=true
and isArchived=false
.
Downloading Translated Jobs
To download the completed translations, first initiate an export of the Job using the export endpoint. This will set theisProcessing
value to 1
.
isProcessing
value will be set to 0
(or -2
in the case of an export error).