Skip to main content
PATCH
Move or reassign one technician without replacing the visit

Authorizations

Authorization
string
header
required

Existing Breezy API key. Grants all published reads and scheduling writes in its associated company. No app permission scopes.

Headers

Idempotency-Key
string
required
Pattern: ^[A-Za-z0-9_-]{8,128}$

Path Parameters

id
string<uuid>
required

Body

application/json
expected_revision
string
required

Revision from the schedule visit read or previous successful command.

Pattern: ^[a-f0-9]{64}$
team_member_id
string<uuid>
starts_at
string<date-time>
Pattern: ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(?:\.\d{1,6})?(?:Z|[+-]\d{2}:?\d{2})$
ends_at
string<date-time>
Pattern: ^\d{4}-\d{2}-\d{2}T\d{2}:\d{2}:\d{2}(?:\.\d{1,6})?(?:Z|[+-]\d{2}:?\d{2})$
customer_notification
object | null
allow_outside_window
boolean
default:false

Response

Committed visit and notification outcome. Replays retain the original visit snapshot; reread for current state.

data
object
required
notification
object
required

The scheduling change is committed regardless of notification outcome. UNKNOWN may have reached the provider and is never automatically resent. SUPPRESSED means the visit or recipient changed before delivery.

meta
object
required

Generation time and company timezone. generated_at is not a snapshot or synchronization token.