# OpenTable APIs (slim)

> OpenTable's partner APIs let approved partners search restaurant availability and make, change and cancel reservations, for diners through the Consumer API or for restaurants' voice agents through the In-House Booking API, with OAuth 2.0 client credentials.

- Full: https://www.anchorterminal.com/tools/opentable.md (~5,650 tokens) · this version ~1,580 tokens · JSON https://www.anchorterminal.com/tools/opentable.json · canonical https://www.anchorterminal.com/tools/opentable
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · Updated: 2026-10-14

**E · 38.6/100 · rank #994 of 1076 · #5 in Restaurant & local bookings · not agent-ready · confidence medium**


Assessment: The public documentation covers diner-side and venue-side booking in detail, with slot locks, policy endpoints, error tables and an X-Request-Id header for safe retries. Access needs partner approval and a contract, rate limits and prices are not published, and the status page and main website could not be read.

## Facts

- Kind: HTTP API · vendor: OpenTable · category: Restaurant & local bookings · legal entity: not named · provenance 64/100
- Endpoint: `https://platform.opentable.com` (HTTP)
- Auth: OAuth · pricing: Your plan · x402: no · licence: Proprietary service under each partner's agreement with OpenTable and the Platform Policy published in the API documentation
- Probe metrics: not measured yet (probes haven't run)
- Surface graded: The partner REST APIs documented at https://docs.opentable.com, mainly the Online Booking API (Consumer API v2) and the In-House Booking API. No official MCP server was found
- Diner or venue: Both. The Consumer API books on behalf of diners for affiliates and restaurant websites. The In-House Booking API, CRM, POS and Sync APIs act for the restaurant
- Booking flow: Availability search (window up to 720 minutes), availability metadata, experiences and totals, slot lock with DELETE to release, make reservation, modify, cancel, find reservation, payment profile
- Deposits and fees: Policy endpoints return per-guest deposits, card holds, cancellation penalties and cut-offs. Card details are tokenised with Spreedly (v2) or Stripe. Restaurants may pass a 2 per cent OpenTable Service Fee to diners
- Credentials: OAuth 2.0 client credentials per partner, sandbox at oauth-pp.opentable.com and production at oauth.opentable.com. No per-endpoint scopes are documented for the client credentials grant
- Environments: Sandbox (pre-production) with curated responses and test restaurant IDs, and production after certification
- Rate limits: Not published. They vary by endpoint and use case and come from the OpenTable representative. 429 appears in the CRM error tables
- Transport: HTTPS only, TLS 1.3 only from 6 October 2025, LZ4 and gzip compression supported, Akamai as CDN
- Webhooks: Reservation webhooks for POS and Sync partners (v3 released February 2025), HTTPS on port 443 with Basic or Bearer authentication
- Versions: Consumer API v1 remains supported with no deprecation date. v2 is recommended for new integrations. CRM moved to v3 in April 2024

- Scores: Reliability 35, Performance pending, Schema & documentation 61, Agent ergonomics 69, Security & auth 33, Payments & pricing 5, Task success pending, Maintenance & community 5, Transparency & trust 42 · total over the 7 assessed categories
- Why: Reliability, Graded as a hosted API. · Schema & documentation, No OpenAPI file. · Agent ergonomics, Availability takes a party size, a start time and forward and backward windows up to 720 minutes, and experiences are opt-in. · Security & auth, OAuth 2.0 client credentials per partner, with the secret in the Authorization header and rotation on OpenTable's request. · Payments & pricing, No x402, MPP or L402 (0). · Maintenance & community, The change log has three undated entries (Spreedly support in Booking API v2, Stripe details for backward-compatible bookings, service fees)… · Transparency & trust, Closed service.
- Sources: 5, open questions: 5, both in the full twin
- Capabilities: booking.availability, booking.reservations, booking.venue, crm.records
- JSON: https://www.anchorterminal.com/api/v1/tools/opentable.json
- Verify (for the vendor): the badge `https://www.anchorterminal.com/badges/opentable.svg` or a link to https://www.anchorterminal.com/tools/opentable from a page on opentable.com or one of its subdomains, then `POST https://www.anchorterminal.com/api/v1/verify` `{"slug", "url"}` or `verify_listing` at /mcp; re-checked weekly, no effect on the grade. Snippets in the full twin.

## Before you call it

1. Lock the slot before calling Make Reservation, since the lock and its reservation_token expire within 5 minutes
2. Send a unique X-Request-Id on every POST, PUT and PATCH so a retried booking is not duplicated
3. Fetch booking and cancellation policies before booking and show any deposit, hold or service fee to the diner
4. Use the Consumer API for diner bookings and the In-House Booking API only for a restaurant's own voice or phone channel
5. Ask the OpenTable representative for the rate limit of each endpoint before going live

## Connect

```bash
curl "https://oauth-pp.opentable.com/api/v2/oauth/token?grant_type=client_credentials" -H "Authorization: Basic BASE64_CLIENT_ID_AND_SECRET"
```
Full config and headless snippets are in the full page. Through letme (picks today, calling later): https://letme.dev/opentable

## Similar tools

| Tool | Grade | Score | Shared capabilities | Slim |
| --- | --- | --- | --- | --- |
| Eat App Partner API | D | 53.4 | booking.reservations, booking.availability, booking.venue, crm.records | https://www.anchorterminal.com/tools/eat-app.min.md |
| TheFork B2B API | E | 43.6 | booking.reservations, booking.availability, booking.venue, crm.records | https://www.anchorterminal.com/tools/thefork.min.md |
| SevenRooms | F | 17.7 | booking.venue, booking.reservations, booking.availability, crm.records | https://www.anchorterminal.com/tools/sevenrooms.min.md |
| TableCheck API | C | 57.1 | booking.availability, booking.reservations, booking.venue | https://www.anchorterminal.com/tools/tablecheck.min.md |
| Resy | F | 10.3 | booking.reservations, booking.availability, booking.venue | https://www.anchorterminal.com/tools/resy.min.md |


## Panel reviews (0, desk reviews from public material, no calls made)