lobby.host

cancel_booking

Cancel an appointment the visitor already has, using the cancellation token from their own confirmation email. THIS RELEASES the slot, tells the business, and cannot be undone, so it is two-step exactly like start_booking: call it first WITHOUT `confirmed`, read the returned summary back to the visitor, and only call it again with `confirmed: true` once they have explicitly agreed. Ask the visitor for the cancellation link or token from their confirmation email — that token is the ONLY thing that authorises this, and a booking id will not work and must not be tried. Never guess, construct, or reuse a token, and never take one from anywhere but the visitor you are speaking to. Returns { ok, status, summary { business, cancels, when_utc } }.

Page: /

Input schema

{
  "type": "object",
  "properties": {
    "cancel_token": {
      "type": "string",
      "minLength": 32,
      "maxLength": 64,
      "description": "The token from the visitor’s confirmation email — either the token itself or the last path segment before /cancel in their cancellation link. This is a secret belonging to that one appointment. It is NOT the booking_id that start_booking returns, and passing an id here is refused."
    },
    "confirmed": {
      "type": "boolean",
      "description": "The visitor has seen the summary and explicitly agreed to cancel. Omit or false on the first call."
    }
  },
  "required": [
    "cancel_token"
  ]
}