curl -X PATCH https://api.bodha.run/api/v1/stops/665f1a2b3c4d5e6f7a8b9c0e \
-H "X-API-Key: bk_live_..." \
-H "Content-Type: application/json" \
-d '{
"recipient": { "phone": "+14155559999" },
"notes": "Ring doorbell twice",
"status": "completed"
}'
Stops
Update Stop
Update recipient, notes, custom properties, or status on a stop.
PATCH
/
stops
/
{stopId}
curl -X PATCH https://api.bodha.run/api/v1/stops/665f1a2b3c4d5e6f7a8b9c0e \
-H "X-API-Key: bk_live_..." \
-H "Content-Type: application/json" \
-d '{
"recipient": { "phone": "+14155559999" },
"notes": "Ring doorbell twice",
"status": "completed"
}'
string
required
The stop’s unique identifier.
string
Delivery notes visible to the driver.
object
Key-value pairs for custom data. Replaces all existing custom properties.
string
Set the stop status:
pending, completed, or missed.curl -X PATCH https://api.bodha.run/api/v1/stops/665f1a2b3c4d5e6f7a8b9c0e \
-H "X-API-Key: bk_live_..." \
-H "Content-Type: application/json" \
-d '{
"recipient": { "phone": "+14155559999" },
"notes": "Ring doorbell twice",
"status": "completed"
}'
Setting
status to completed or missed via the API does not trigger
proof-of-delivery flows. Use this for system-level status syncing, not driver
workflows.