Two lines, or the whole diary.

Check a key works and find out what this deployment can do before you build against it.

What is bookable: services with their durations and LIST prices, the people who perform them, and where. A list price is not a quote — price-preview under Bookings gives the figure a customer will actually be charged.

The times a booking would actually be accepted. Computed from opening hours, the person, the service, holidays, blocked time and what is already booked — so a slot you are offered is one you can take.

Hold a slot briefly while a customer finishes deciding. A reservation is not a booking and expires on its own.

Quote a price, then create, read, reschedule and cancel appointments. Every write goes through the same pipeline the booking page uses, so nothing reached this way behaves differently — and price-preview runs the same pricing code the booking itself runs, so a quote and a charge cannot disagree.

Booking rules, custom forms and the status vocabulary — full admin control for an agent whose key carries the settings.manage scope. Keys minted without it, including every key minted before scopes existed, are refused here and keep taking bookings exactly as before.

The guided-booking wizard — cards, options, and the publish gate, for keys carrying the settings.manage scope. Publishing runs the same validator the panel’s editor runs, and a refusal returns the findings so an agent can repair the flow. The full lesson lives at /developers/flows.

Appointment and revenue figures over a date range, for keys carrying the reports.read scope. The same series the panel’s own reports draw.