Documentation menu
These are pre-release docs from the main branch.

API reference

3 operations in dispatch-connector. Raw spec: openapi.json.

POST/api/v1/dispatch-connector/appointments/{id}/status

POST /api/dispatch-connector/appointments/{id}/status — push one field-service status update. Idempotent via the instant envelope: the same key + payload replays the same stored row (never double-pushes); a foreign-org appointment id is a bare 404.

Parameters

NameInTypeRequiredDescription
idpathstringYes

Request body

PushStatusRequest

Responses

StatusDescription
201
404appointment not visible in scope
409idempotency key reused with a different payload
422unknown status vocabulary
429rate limit exceeded (Retry-After header)

Security: bearer, api_key

GET/api/v1/dispatch-connector/schedule

GET /api/dispatch-connector/schedule — bookings in a bounded window with technician/ticket/client coordinates and the latest pushed field-service status per booking.

Parameters

NameInTypeRequiredDescription
fromquery—No
daysquery—NoWindow length in days (1..=62, default 7).

Responses

StatusDescription
200
403missing dispatch:read scope (keys) or not an org admin (humans)

Security: bearer, api_key

GET/api/v1/dispatch-connector/technicians

GET /api/dispatch-connector/technicians — active technicians with their current (non-expired) skills.

Responses

StatusDescription
200
403missing dispatch:read scope (keys) or not an org admin (humans)

Security: bearer, api_key