Job
Update source
API updated source file for specified job
Job file can be provided directly in the message body.
Please supply jobs in Memsource
header.
For file in the request body provide also the filename in Content-Disposition
header.
If a job from a multilingual file is updated, all jobs from the same file are update too even if their UIDs aren’t listed in the jobs field.
Accepted metadata:
jobs
- required - list of jobs UID reference (maximum size100
)preTranslate
- pre translate flag (defaultfalse
)allowAutomaticPostAnalysis
- if automatic post editing analysis should be created. If not specified then value is taken from the analyse settings of the projectcallbackUrl
- consumer callback
Job restrictions:
- job must belong to project specified in path (
projectUid
) - job
UID
must be from the first workflow step - job cannot be split
- job cannot be continuous
- job cannot originate in a connector
- status in any of the job’s workflow steps cannot be a final
status (
COMPLETED_BY_LINGUIST
,COMPLETED
,CANCELLED
) - job UIDs must be from the same multilingual file if a multilingual file is updated
- multiple multilingual files or a mixture of multilingual and other jobs cannot be updated in one call
File restrictions:
- file cannot be a
.zip
file
Example:
{
"jobs": [
{
"uid": "jobIn1stWfStepAndNonFinalStatusUid"
}
],
"preTranslate": false,
"allowAutomaticPostAnalysis": false
"callbackUrl": "https://my-shiny-service.com/consumeCallback"
}
POST
Update source
Headers
must match pattern ((inline|attachment); )?(filename\*=UTF-8''(.+)|filename="?(.+)"?)
Path Parameters
Body
application/octet-stream · object
Response
200
application/json
Updated
The response is of type object
.
Update source