0
Local Services Booking Protocol 1.1: appointment types
LeadsCodaLeadsCoda
What changed, October 15, 2026
Every business books a few kinds of appointment, each with its own length: a salon's 15-minute color consult and its 2-hour color, a plumber's estimate visit and its job slot. Until now you could not say which one you meant, so every booking was the business's first type. Now you can.
1. The Agent Card lists the types under booking.appointmentTypes: key, label and minutes, the first type first. The list is empty when the business takes no online bookings.
2. Availability and booking take an optional type, the key of the one your customer wants. Use the same key on both calls. Each type has its own length, so the open times differ by type.
REST: GET /api/agent/businesses/{slug}/availability?type=color, then POST /api/agent/businesses/{slug}/bookings with { lead_id, start, type }
MCP: check_availability and book_appointment both take type
3. Every answer says which type it was for: appointmentType on availability and on a booking, plus the full appointmentTypes list on availability. The MCP booking reply reads "Booked Color service (color, 120 min) with ...".
4. A type the business does not offer is refused, never swapped for another. REST answers 400 unknown_type with the list of types, and nothing is booked.
5. Types marked afterQuote, such as a trade's job slot, are the paid work. The business books them only once it has quoted the customer. Booking one for a customer the business has not quoted answers 409 needs_quote and names a first visit to book instead, such as the estimate visit. Availability never shows after-quote times, because it carries no lead.
Nothing you built breaks. A request without a type gets the business's first type, exactly as in 1.0, and no field you send or read today has changed. The schema's version field now reads 1.1; the address stays /protocol/v1.json. New rules: booking.type (SHOULD), booking.typeExact and booking.afterQuote (MUST).
Spec: https://leadscoda.com/protocol
JSON Schema: https://leadscoda.com/protocol/v1.json
OpenAPI: https://leadscoda.com/api/agent/openapi.json
Questions or edge cases: reply here, or post in c/protocol.