Please read carefully about authentication and prerequisites , and take into consideration that some steps might be done by Trados engineering.
Details about what are the rate limits for Trados Cloud Platform API can be found on API rate limits page.
Additional information regarding file and project size limits can be found here.
Note
This small Postman collection can help you get started with the basic project creation flow. For details on Postman setup please see the main Postman page.
In the Create Project endpoint body, the projectTemplate value should be replaced with a valid templateId. From that point on all the necessary identifiers will be automatically populated throughout Postman.
Check the Multi-Region page for regional API details.
Steps to create a basic translation project:
- Create Project
- Add project source file
- Start Project
- List Project's Tasks
- List Project Target Files
- Download File
- Complete Project
- List Projects
Creates a new project.
Endpoint: POST /projects
For running this endpoint you need to supply the required project details (body tab in Postman):
{
"name": "Name of the Project",
"description": "Test Project",
"dueBy": "2021-09-04T08:14:05.858Z",
"projectTemplate": {
"id": "xxxxxxxxxxxxxxxxxxxxxxxx" // Provided by RWS
},
"languageDirections": [
{
"sourceLanguage": {
"languageCode": "en-US"
},
"targetLanguage": {
"languageCode": "fr-FR"
}
}
]
}Source and Target Language Codes can be obtained from here.
The API should respond with:
- HTTP Status Code: 201 Created.
- Body - your project details consisting of
projectId,project name,language direction,locationand other optional fields.
Example:
{
"id": "xxxxxxxxxxxxxxxxxxxxxxxx", // The project identifier.
"name": "Name of the Project",
"languageDirections": [
{
"sourceLanguage": {
"languageCode": "en-US",
"englishName": "English (United States)"
},
"targetLanguage": {
"languageCode": "fr-FR",
"englishName": "French (France)"
}
}
],
"location": {
"id": "xxxxxxxxxxxxxxxxxxxxxxxx",
"name": "Project Location"
}
}
If your company has multiple divisions, you can imagine a hierarchy like this:
YOUR COMPANY
- Marketing Division
- Management Division
- HR Division
If you want to create projects for different divisions, this can be done by using the location parameter, which will be added in the body. When location is not set, the system will try to create the resource in the higher folder in the hierarchy, the Root folder. It might not have access to that folder and the request will fail with forbidden error.
{
"name": "Name of the Project",
"description": "Test Project",
"dueBy": "2021-09-04T08:14:05.858Z",
"projectTemplate": {
"id": "xxxxxxxxxxxxxxxxxxxxxxxx" // Provided by RWS
},
"languageDirections": [
{
"sourceLanguage": {
"languageCode": "en-US"
},
"targetLanguage": {
"languageCode": "fr-FR"
}
}
],
"location": "xxxxxxxxxxxxxxxxxxxxxxxx" // Provided by RWS
}Using this request your project will be created in the specified Division and it will be visible only there.
Detailed information about location and folders can be found on the How to use location and folders page.
More details about this endpoint can be found here.
Adds a source file to the project.
Endpoint: POST /projects/{projectId}/source-files
For running this endpoint you need to:
- Replace
{projectId}from the URL with the identifier received from the Create Project endpoint response:
- Add the file to the request body.
- Complete the details from Body tab - Properties field.
Properties field:
{
"language": "en-US",
"type": "native",
"role": "translatable",
"name": "nameOfTheFile.extension"
}Responses:
- HTTP Code 201 Created.
- Body - a list with the identifier, name and role of the file.
More details about this endpoint can be found here.
Starts a project.
Endpoint: PUT /projects/{projectId}/start
For running this endpoint you need to:
- Replace
{projectId}from the URL with the identifier received from the Create Project endpoint response:
Responses:
- HTTP Code 202 Accepted
More details about this endpoint can be found here.
List the tasks of a specific project. If all the tasks have the status completed, all the files are translated.
Endpoint: GET /projects/{projectId}/tasks
For running this endpoint you need to:
- Replace
{projectId}from the URL with the identifier received from the Create Project endpoint response:
Use ?fields=taskType if you want to observe the task name.
Responses:
- HTTP Code 200 Ok.
- Body - a list with task identifier and status.
Example:
{
"items": [
{
"id": "613f621fe5ed2804ba31870e",
"status": "completed",
"taskType": {
"id": "607932f25c7cc701241f0f60",
"key": "scan",
"name": "File Type Detection"
}
},
{
"id": "613f623040d9943308ef7c3b",
"status": "completed",
"taskType": {
"id": "607932f3ce8af15851b70205",
"key": "convert",
"name": "File Format Conversion"
}
},
...
],
"itemCount": 11
}
More details about this endpoint can be found here.
Retrieves the target fileId for a project and the latest version for the translated file.
Endpoint: GET /projects/{projectId}/target-files
For running this endpoint you need to:
- Replace
{projectId}from the URL with the identifier received from the Create Project endpoint response:
Responses:
- HTTP Code 200 Ok.
- Body - a list with objects that contain:
- source file and target file identifiers
- source and target languages
Example:
{
"items": [
{
"id": "613f623ae5ed2804ba318a40", // This is the target file identifier.
"latestVersion": {
"id": "613f628540d9943308ef8497", // This is the file version identifier.
"type": "native"
}
},
{
"id": "613f623ae5ed2804ba318a43",
"latestVersion": {
"id": "613f628a40d9943308ef84cd",
"type": "native"
}
}
],
"itemCount": 2
}
More details about this endpoint can be found here.
Downloads the translated file.
Endpoint: GET /projects/{projectId}/target-files/{targetFileId}/versions/{fileVersionId}/download
For running this endpoint you need to:
- Replace
{projectId}from the URL with the identifier received from the Create Project endpoint response - Replace
{targetFileId}from the URL with the identifier received from the List Project Target Files endpoint response - Replace
{fileVersionId}from the URL with the identifier received from the List Project Target Files endpoint response
Responses:
- HTTP Code 200 OK.
- Body - the translated file. The file can be also saved from Save Response option.
More details about this endpoint can be found here.
Marks a project as completed.
Endpoint: PUT /projects/{projectId}/complete
For running this endpoint you need to:
- Replace
{projectId}from the URL with the identifier received from the Create Project endpoint response
Responses:
- HTTP Code 204 No Content.
More details about this endpoint can be found here.
Retrieves a list of all the projects in the account.
Endpoint: GET /projects
For running this endpoint make a request to:
Responses:
- HTTP Code 200 OK.
- Body - a list of projects with details consisting of project identifier, project name, language direction, location and other optional fields
Example:
{
"items": [
{
"id": "xxxxxxxxxxxxxxxxxxxxxxxx",
"name": "Translation Project 1",
"languageDirections": [
{
"sourceLanguage": {
"languageCode": "en-US",
"englishName": "English (United States)"
},
"targetLanguage": {
"languageCode": "fr-FR",
"englishName": "French (France)"
}
}
],
"location": {
"id": "xxxxxxxxxxxxxxxxxxxxxxxx",
"name": "Project Location"
}
},
{
"id": "xxxxxxxxxxxxxxxxxxxxxxxx",
"name": "Translation Project 2",
"languageDirections": [
{
"sourceLanguage": {
"languageCode": "en-US",
"englishName": "English (United States)"
},
"targetLanguage": {
"languageCode": "fr-FR",
"englishName": "French (France)"
}
}
],
"location": {
"id": "xxxxxxxxxxxxxxxxxxxxxxxx",
"name": "Project Location"
}
}
],
"itemCount": 2
}
More details about this endpoint can be found here.