Add Target File Version
Adds a new version of the target file. Only the native and bcm file formats are accepted. For the sdlxliff files, you should use the Import Target File endpoint. More information about file formats can be found on the File formats page. Additional details on BCM files can be found here.
The version is added on the task represented by taskId. To be able to execute the add operation the task should be assigned and accepted by user. If the task is automatic, it is possible to add a target file version only if the status is inProgress.
The added file versions need to respect the output file type declared by the task type of the enclosing task. On the Rules for sequencing tasks correctly page from the official RWS Documentation Center, you can find out what output file type is supported by each task.
For adding a target file version using an extension task, the configuration of the task type must declare the scope's value as "file".
The multipart parameters in the body should respect and strictly follow the order specified in our documentation.
Consider the file and project size limit when uploading files.
Query parameters
A comma separated list of fields to include in the response. Every value in the list should either consist of a top-level property name (excluding the items envelope for endpoints returning lists) or refer to a property of a top-level property of type object, in the following form: "toplevelpropertyname.subpropertyname". When this query parameter is omitted, default resource representations are returned (excluding fields marked as optional). The same applies to nested objects when just specifying the top-level property name, without explicitly listing sub-property names. When specifying the fields query parameter, only the specified fields are returned. The id property is always returned.
Headers
The bearer access token provided by Auth0.
The identifier of the account where the request is executed.
Response
Created