Skip to main content
POST
Book a meeting — confirm an offered slot, or let the engine pick

Authorizations

x-api-key
string
header
required

API key from Settings > API Keys or POST /v1/api-keys. Format f9_live_<32 hex chars> (live) or f9_test_<32 hex chars> (sandbox — no real sends, ever). Legacy wcrm_live_ / wcrm_test_ keys still authenticate but are no longer issued. Shown once at creation; only a hash is stored.

Body

application/json

Exactly one shape: slot_token (confirm an offered slot — from POST /v1/scheduling/slots/search, optionally with the reservation_id holding it and, for a shared-exposure slot, assign_user_id) OR member_ids (+ optional policy_id, from, to: the engine picks the rep and the earliest slot). Both take attendee, meeting and an optional record_id (the CRM record this meeting is about; carried on the appointment.* webhook events).

slot_token
string
reservation_id
string<uuid>
assign_user_id
string<uuid>
member_ids
string<uuid>[]
policy_id
string<uuid>
from
string<date-time>
to
string<date-time>
attendee
object
meeting
object
record_id
string<uuid>

Response

Booked

success
enum<boolean>
Available options:
true
data
object
meta
object