SevenRooms vs TheFork B2B API

SevenRooms

SevenRooms runs reservations, table management and guest CRM for hospitality venues, with a Statuspage history that includes its API and a trust centre listing SOC 2 and PCI DSS. There is no public API or MCP server an outside agent can call today. The API serves venues and approved partners, and even its documentation needs a provisioned account.

TheFork B2B API

A venue-side API with a generated OpenAPI 3.1 schema, an llms.txt written for agents and nine OAuth scopes down to read-only availability. It acts for restaurants and their vendors, not diners, needs partner approval, cannot take card guarantees, and has no public status page, changelog or published prices.

SevenRooms

1. Don't plan to call SevenRooms from another agent. To book for a diner, use the venue's booking widget with the person, or a booking channel the venue lists
2. If you work for a venue or vendor, apply through the SevenRooms partnerships form before planning an integration

TheFork B2B API

1. Read hasPaymentGuaranteeRequirement in the timeslots response before booking, since the API cannot take a card
2. Check the status field after creating a reservation and treat REQUESTED as unconfirmed
3. Send the timeslot datetime unchanged as mealDate, because times are the restaurant's local time
4. Check for an existing reservation before retrying a failed POST, as no idempotency key exists and 409 signals DOUBLE_BOOKING
5. Cache the access token for its 8,600 seconds and do not request a new one while it is valid