To add one or more files to an existing Codyt project.
Based on the project settings, the operation initiates translation workflows by saving files to the project, marking them online, conducting pre-translation and word count, and creating and assigning jobs.
...
files | An array containing one or more records, each describing a file to be uploaded. These records include a unique token referencing the uploaded file. For example:
See detailed description further down. | object[], Mandatory | ||
src | The source language code. This must be a valid project language. | string, Mandatory | ||
trgs | The languages to translate to. These must be valid project languages. Example:
| string[], Mandatory | ||
deadline | Optional deadline for completion of work. Deadlines are assigned to the jobs that are created with the workflow. Example:
| datetime?, Optional | ||
workflow | Optional, selects
| string, Optional | ||
allowUpdates | Optional. Default is true.
| bool?, Optional | ||
jobsCfs | Optional custom fields to assign to all jobs created for a file’s workflow. See Custom Field Collection Record for details. Note: You reference a CF by either its “id” or its “title” (name). Example:
| object[], Optional | ||
maxFilesInJob | This parameter is applicable only to Standard projects, with a default value of 100. The maximum is 1000. It is designed for scenarios involving the submission of a large number of files. The system will group the files into jobs, ensuring that no single job contains more than the specified number of files. If the total exceeds this limit, multiple jobs and workflows will be created automatically. Note: For Codyt jobs, this parameter is not applicable, as Codyt always creates one workflow per file. | int, Optional | ||
callbackurl | Specify a URL which will be called upon success or failure of operation. This makes polling for operation status unnecessary. See Callbacks (with asynchronous operations) | Optional |
...