Create an Acuity Scheduling appointment after checking real-time availability via the API
domain: developers.acuityscheduling.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Authenticate requests with HTTP Basic Auth using your Acuity User ID and API Key.
Call GET /availability/dates for the target appointmentTypeID and month to find which dates have open slots.
Call GET /availability/times for a specific date to retrieve the actual bookable time slots, matching what clients see on the public scheduling page.
Optionally call GET /availability/check-times to validate a specific slot is still valid immediately before booking, checking the returned valid boolean and any reason for invalidity.
POST /appointments with the appointmentTypeID, chosen datetime, and required client fields (firstName, lastName, email); include fields for any custom intake-form responses configured on that appointment type.
Known gotchas
Availability can change between the /availability/times check and the /appointments POST under concurrent bookings — always re-validate with check-times or handle a booking-conflict error rather than assuming the earlier slot list is still accurate.
Appointment types with custom intake forms will reject a booking that omits their required custom fields, so the create-appointment payload must be built per appointment type rather than using one fixed schema for all types.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?