Webhook Events

Required

The scheduling provider must send webhook events to Seamlr when shifts change.

Webhook Endpoint

POST /api/v3/integrations/{provider}/webhook

Event Types

shift.create

New shift available for staffing. Seamlr will fetch the shift details and create a matching job.

shift.update

Shift details changed (time, slots, location, etc.). Seamlr will update the internal job and notify assigned candidates.

shift.delete

Shift cancelled or removed. Seamlr will cancel the job and notify assigned candidates.

Payload Schema

Note

All webhook payloads include a traceId for request tracing.

{
  "event": "shift.create",
  "providerId": "550e8400-e29b-41d4-a716-446655440000",
  "content": {
    "shiftId": "6ba7b810-9dad-11d1-80b4-00c04fd430c8"
  },
  "traceId": "6ba7b811-9dad-11d1-80b4-00c04fd430c8"
}

Field	Type	Description
event	string	Event type (shift.create, shift.update, shift.delete)
providerId	string (UUID)	Provider organization identifier for multi-tenant routing
content.shiftId	string (UUID)	Shift ID in the provider system
traceId	string (UUID)	Unique identifier for request tracing

Webhook Response

Seamlr responds immediately with 200 OK and queues the event for processing:

{
  "received": true
}

Processing Flow

1. Provider sends webhook to Seamlr endpoint

2. Seamlr responds with 200 OK immediately (< 500ms)

3. Event is queued for processing

4. Seamlr fetches full shift details via Provider API

5. Seamlr creates/updates internal job and notifies candidates

Tip

The webhook acknowledgment happens before processing. Check the Internal Architecture for processing SLAs.