Skip to main content
Any API POST/PUT request won’t trigger a workflow.

GET /workers

Retrieves all workers. By default, this excludes non-current and deleted workers. Example: GET /workers?includeSkills=TRUE Parameters: Response:
Response fields:

POST /worker

Creates a new worker record. Required fields: FirstName, LastName Auto-generated: CarerId Side effects: Creates availability by default and compliance items based on org settings. Fields that CANNOT be set: CarerId, CarerCode, WebIdHash, WebPassword, WebLastLogin, WebPhoneType, WebGPSLong, WebGPSLat, WebGPSDate, WebAvailability, WebPushToken, Status, _LastAppUpdateSeenTime, _LastAppUpdateVersion, _LastModTime, _LastModUser, _CreateTime, _CreateUser, _RecordLocked, LinkingDBId Content-Type: application/json Request body:
The POST body is wrapped in an array, unlike the PUT body which is a plain object.
Successful response format is not documented. No example response is provided in the source.

PUT /worker

Updates an existing worker record. Required fields: CarerId (plus at least one field to update, otherwise returns an error) Fields that CANNOT be edited: CarerId, CarerCode, WebIdHash, WebPassword, WebLastLogin, WebPhoneType, WebGPSLong, WebGPSLat, WebGPSDate, WebAvailability, WebPushToken, _LastAppUpdateSeenTime, _LastAppUpdateVersion, _LastModTime, _LastModUser, _CreateTime, _CreateUser, _RecordLocked, LinkingDBId
The PUT non-editable list does NOT include Status (unlike POST), suggesting Status may be updatable via PUT.
Content-Type: application/json Request body: