Webhooks are a good way to set up integrations with Eastridge Cloud. You can subscribe to certain events and when those events are triggered, we send an HTTP POST request to the webhook URL. For example, you might want to kick off a new user set up process when a worker completes onboarding.
Events
| Name | Description |
|---|---|
client_order_assignment_ended | Triggered when a worker's assignment is ended |
client_order_assignment_extended | Triggered when a worker's assignment is extended |
client_order_assignment_onboard_completed | Triggered when a worker completes onboarding |
client_order_present_worker_offer_accepted | Triggered when an offer is accepted |
client_order_assignment_labor_tag_updated | Triggered when a worker's job is created, updated or retired |
Payload
The standard payload contains the name of the webhook and id of the affected model.
{
"id": 258413,
"name": "client_order_assignment_onboard_completed"
}
For webhooks that can be the result of similar related actions (like client_order_assignment_labor_tag_updated), an action field is included in the payload.
{
"id": 258413,
"name": "client_order_assignment_labor_tag_updated",
"action": "create"
}
Lastly, for webhooks that are the result of an update, they get the new and old values of all the fields that were updated.
{
"id": 252840,
"name": "client_order_assignment_labor_tag_updated",
"action": "update",
"updates": {
"client_scheduling_group_instance_id": {
"old": 250009,
"new": 250008
}
}
}