Webhook Reservation No Show
When BodySpec determines that a reserved appointment was a no-show, it sends a POST request with this payload to your registered webhook URL. BodySpec does not record attendance, so this is inferred and deliberately conservative: it fires only once the appointment time has passed with no published results, the location has finished its day, and a later appointment at the same location that day produced results. An appointment that never meets that bar stays pending_scan and no event is sent. If results are published later, a results_ready event follows and supersedes this one.
postWebhookreservation_no_show
Payload
Example payload
{
"data": {
"appt_id": "e8c91d4a2b7f3e6c8d0a5b9f1c3e7d2a",
"no_show_time": "2024-03-20T19:05:12-07:00",
"service_id": "8d0e0a1f561f4ec69dbca50ea14336d",
"start_time": "2024-03-20T14:00:00-07:00",
"user_id": "a5950beea2a7487fb79cfdbeb77fa555"
},
"event_id": "9c1f4e27ab8d43e6b5f2a0c7d8e91b34",
"event_type": "reservation_no_show",
"partner_id": "pk_acme"
}Response
Successful Response
unknown required
Changes
Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.