Skip to main content
POST

Request

See also Job-API-Object to see properties of a job.
To directly assign a user, set the worker property in the job to the worker’s username. To get the worker’s username, retrieve the username in Member-API-Object, for example via /getaccounts.
jobs
array
required
An array of objects, each object needs to confirm the Job API Object schema.Important Notes:
  • Do not set the id field, this will be set automatically upon creation.
  • You can optionally set the uidSecondary field as a custom external identifier. If a job with the same uidSecondary already exists for the company, the existing job will be updated instead of creating a new one.
  • To assign a job during creation, set the worker field to the worker’s username or set receiverUid to the worker’s UID.
  • For custom job fields, use either customFields as an array of { "key": "...", "val": "..." } objects, or use custom_<fieldName> for single fields.
sendRouteChange
boolean
default:"false"
If true, assigned and day set to today, notifies assignee immediately of jobs being updated. The list of jobs will be updated automatically on their device.
autoassign
boolean
default:"false"
Indicates that the created jobs should automatically be assigned to a member. It will choose the nearest member that is available, taking the shift and day-route into account.
isTemplate
boolean
default:"false"
If set to true, creates jobs as templates rather than regular jobs. Job templates can be reused to create multiple jobs with the same configuration.

Custom Fields in jobs

Inside each job object, custom fields can be sent in the following format:
  • customFields array (recommended for multiple fields):

Response

status
number
required
Guaranteed to be set. Set to 0 if successful.
jobs
array
required
The array of all jobs created by this request.