Reference

Endpoint reference

Every endpoint the API exposes, grouped by resource.

GET/v1/Index: the API name, version, server time, and the partner endpoints.

POST/v1/venues/searchSearch venues for a vertical (dining, fitness, entertainment, travel).

POST/v1/availability/searchGet bookable slots for a specific venue, with each restaurant slot's card and cancellation terms.

POST/v1/bookingsCreate a booking for a venue and requested time. Send end_user to book signed in as a person with a connected session.

GET/v1/bookings/{booking_id}Read a booking and its current status.

POST/v1/bookings/{booking_id}/continueSubmit an OTP or other action to advance a booking.

POST/v1/bookings/{booking_id}/modifyMove a confirmed booking's date/time, party size, or seating preference. Fields are independent — send only the field(s) you want to change. OpenTable only; other providers answer 422 modify_unsupported.

POST/v1/bookings/{booking_id}/cancelCancel a booking. A confirmed booking is cancelled at the venue on OpenTable only; elsewhere it stays confirmed with error_code cancellation_unsupported.

POST/v1/sessionsConnect a person's own provider account (Resy). Texts them a code. See Sessions.

POST/v1/sessions/{id}/verifySend the code the person received; the session becomes active.

GET/v1/sessionsList sessions. Filter with ?end_user=, &provider=, &state=.

GET/v1/sessions/{id}Read one session.

DELETE/v1/sessions/{id}Disconnect a session. The saved sign-in is destroyed.

GET/v1/sessions/{id}/cardDoes the person's provider account have a card on file? Returns has_card.

GET/v1/sessions/cardThe same card check, by ?end_user= (and &provider=, default resy).