- Change Appointment attendance status
Change the attendance status of one Appointment without resending the full Appointment. The body field is attendance (not visit_attendance). The supported statuses are -1 (did not come), 0 (waiting), 1 (came), and 2 (confirmed). Read the current status from the Appointment first.
The Business User needs record_form_access and edit_records_access for this Location. The Appointment must fall within the Location's records_edit_last_days_count editing window (-1 means no history limit). A request can also be rejected while online payment is pending, by payment policy, or when a printed sale receipt would be invalidated. With a printed receipt, only 1 and 2 remain eligible statuses. Submitting the current status leaves it unchanged.
Appointments linked into one visit share an attendance group. Changing one Appointment can update the status of other Appointments in that visit and trigger related payment, loyalty, and notification processing. The records response field contains timetable change data; it is not a per-ID bulk result.
For a bounded bulk workflow, select a finite set of Appointment IDs, read each Appointment and confirm its Location, current status, and visit link, then send one request per distinct attendance group. Re-read affected Appointments after each change, record successes and failures per group, and stop or report on a failed request. This endpoint offers no atomic bulk operation or all-or-nothing rollback.
- Mock serverhttps://developer.alteg.io/_mock/en/b2b-v1/openapi/locations/{location_id}/appointments/{record_id}/attendance
- Productionhttps://api.alteg.io/api/v1/locations/{location_id}/appointments/{record_id}/attendance
curl -i -X POST \
'https://developer.alteg.io/_mock/en/b2b-v1/openapi/locations/{location_id}/appointments/{record_id}/attendance' \
-H 'Accept: application/vnd.api.v2+json' \
-H 'Authorization: Bearer <YOUR_Bearer {PartnerToken}, User {UserToken}_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"attendance": 1
}'{ "success": true, "data": { "attendance": 1, "records": [] }, "meta": [] }