Bookings›Set job priority (scheduling staff)
Set job priority (scheduling staff)
Sets the P0–P3 priority on a non-archived, non-completed job (Owner / Administrator / Booking Coordinator). Allowed values: "p0" (emergency, interrupt-driven) | "p1" (top — displaced only by p0; may carry an sla_deadline arming auto-escalation) | "p2" (standard) | "p3" (deferrable, first displacement victim). sla_deadline is only valid with p1 and must be in the future (business-local naive datetime); moving away from p1 disarms the SLA clock. Accepts UUID or short_code in :id.
Arguments
idstringpathrequired
Job request ID or short_code
notestringbodyoptional
Optional justification (max 500 chars) — recorded on the activity trail
and the priority_changed webhook. Recommended when de-escalating an
SLA-escalated job (audit provenance).
priorityenumbodyrequired
New P0–P3 priority level. p0=emergency, p1=top, p2=standard, p3=deferrable.
sla_deadlinestringbodyoptional
SLA deadline (business-local naive datetime) — only with priority=p1;
(re)arms the auto-escalation clock. Omitted on a p1 change keeps any
stored deadline; changing away from p1 disarms SLA entirely.
PATCH/v1/job-requests/{id}/priority
curl -X PATCH "https://api.crisphive.com/v1/job-requests/9b2f6c3e-1a4d-4f0a-8f2e-7c5d1b3a9e01/priority" \ -H "Authorization: Bearer chsk_test_4eC8xQ9mZ2pL7Ka0rT" \ -H "Content-Type: application/json" \ -d '{ "note": "Please call on arrival.", "priority": "p1", "sla_deadline": "2030-06-14T17:00:00" }'
Request body
{
"note": ,
"priority": ,
"sla_deadline":
}
Bearer