A scenario that follows a project throughout its entire life cycle, from its creation to its completion.
Before you begin
Make sure that you have the appropriate permissions to create project groups. Otherwise,
WorldServer will return a 403 Forbidden status code.
Also, you need to use already uploaded assets or to upload new assets. If you want to use already uploaded assets, you need the internalName of each file. If you want to use new assets, upload them into WorldServer.
After you upload an asset through the API, the response includes an
internalName property. Take a screen shot of it or write down its value. You will need it in all operations involving uploaded assets.
Important: The response to the upload request is the only place where you can find out the internalName of an asset. If you forgot to save the internalName of an already uploaded asset, you can no longer retrieve it.
Procedure
- Create a new project group.
You can find the ID of your new project group in the response.
- Translate the project.
Your project group can have one or more projects in it, depending on the number of target locales you selected when creating it. To get the IDs of all the projects in your project group, make a GET call to the following endpoint and write down the appropriate IDs in the response: <protocol>://<ws-host>:<ws-port>/ws-api/v1/<projectGroupId>?token=<sessionId>
- Download the translated assets.
In the request body, include the ID of the project group,
PROJECT_GROUP as the resource type, and
TARGET as the asset location type.
Note: If you would like to manage the assets of each project individually, include the ID of each project, PROJECT as the resource type, and TARGET as the asset location type.
- Complete the project.
Note: If the translation does not meet your requirements, you can reject it by using the same API call. In this case, you need to specify the ID of the Rejected transition from the project workflow.