Look up upcoming bookings
Finds confirmed future bookings of the workspace by invitee identity — the same identity check assistants use before rescheduling or cancelling. Provide at least one of phone, email, name.
A match is only returned when the identity is strong enough: a matching phone number alone is sufficient (match_basis: "phone"), while email and name must BOTH match (match_basis: "email+name"). Phone numbers are compared E.164-tolerantly (leading 00 is treated as +, suffix match on the last 8+ digits), email case-insensitively and exactly, names leniently by word tokens.
Required scope: bookings:read (keys without scope restrictions have full access).
Authorizations
API key (fam_..., created under Settings → API Keys) or an OAuth 2.0 access token (fam_at_...). Keys can be restricted to scopes such as assistants:read, calls:write, campaigns:write, automations:read, dashboards:read, dashboards:write, leads:write, segments:write, loop:read, loop:write, phone_numbers:write, sip_trunks:write, knowledge:write, voices:read, billing:read, settings:write, platform:read, platform:write; a *:write scope implies the matching *:read. Automation and dashboard endpoints also accept the legacy calls:* scope. Keys without scope restrictions have full access.
Body
- Option 1
- Option 2
- Option 3
Response
Matching upcoming bookings, earliest first.