Jobs are created as "unassigned" by default and are queued in the vWork client ready for the dispatcher to assign to a time and worker.
Alternatively, you can pre-assign the job to a worker by setting the worker_id and planned_start_at values. (If you do not supply a planned start at, but do specify a worker, the job will be assigned to the worker straight away.)
To create a job with a worker that should be started immediately, you can send either worker_id or worker_third_party_id as per the following examples:
<worker_id>4016</worker_id><worker_third_party_id>steverino</worker_third_party_id>If you wish to assign the job to a worker now, but have the job scheduled for a future time, you need to also include the planned_start_at as per the example below:
<worker_id>4016</worker_id>
<planned_start_at>2019-12-22T10:15:00+13:00</planned_start_at>worker_name cannot be used to assign a job with this API: a request that includes it is rejected with a 422 error. Use worker_id or worker_third_party_id instead. (The Templated Job API does accept worker_name.)
If the job belongs to one or more groups, the worker must belong to at least one of them, otherwise the request is rejected with a 422 error.