# OpenTable APIs > 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. - Canonical: https://www.anchorterminal.com/tools/opentable - Markdown: https://www.anchorterminal.com/tools/opentable.md (~5,650 tokens) - Slim: https://www.anchorterminal.com/tools/opentable.min.md (~1,580 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/opentable.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-14 ## Overview **Grade 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 | Field | Value | | --- | --- | | Vendor | OpenTable (https://www.opentable.com) | | Kind | HTTP API | | Category | Restaurant & local bookings (https://www.anchorterminal.com/categories/local-bookings) | | Transport | HTTP | | Endpoint | `https://platform.opentable.com` | | Auth | OAuth · Partner approval required. A partner applies through OpenTable's become-a-partner form, the partnerships team reviews the application, and approved partners receive sandbox credentials and restaurant IDs in a welcome email. Tokens come from the OAuth 2.0 client credentials grant at https://oauth-pp.opentable.com (sandbox) or https://oauth.opentable.com (production), with the client ID and secret Base64-encoded in the Authorization header. The Platform Policy forbids sharing credentials and says OpenTable may require rotation. Restaurants connect a partner through an OAuth or unique-identifier onboarding flow in the Integrations Marketplace. | | Pricing | Your plan (Your plan) · No API prices are published. Use is governed by each partner's agreement with OpenTable, and the docs say new implementations may need additional contracting and certification. A sandbox is granted after approval. The change log describes a configurable OpenTable Service Fee (shown to diners as 2 per cent) that restaurants may pass on to diners on experiences, deposits and card holds (https://docs.opentable.com/). | | x402 | No · No x402, MPP or L402 in the public API documentation (checked 2026-10-14). | | Licence | Proprietary service under each partner's agreement with OpenTable and the Platform Policy published in the API documentation | | Docs | https://docs.opentable.com | | llms.txt | not found | | 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 | | Capabilities | booking.availability, booking.reservations, booking.venue, crm.records | | Tags | hosted, closed-source, partner-only, rest, oauth, webhooks, sandbox, restaurants | | JSON | https://www.anchorterminal.com/api/v1/tools/opentable.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-14 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 35 | 7.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 61 | 9.9 | | Agent ergonomics | 13% | 16.2 | 69 | 11.2 | | Security & auth | 14% | 17.5 | 33 | 5.8 | | Payments & pricing | 10% | 12.5 | 5 | 0.6 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 5 | 0.4 | | Transparency & trust (editorial 20, provenance 64) | 7% | 8.8 | 42 | 3.7 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **38.6 → E** | ### Why each score - Reliability 35: Graded as a hosted API. The docs require partners to subscribe to status.opentable.com, a StatusDashboard page, but its components and history load by script and our reader saw only the frame, so it earns part of the line (10 of 20). No readable incident history (5). Rate limits exist but are not published, and the docs send partners to their OpenTable representative (0). 429 appears in the error tables, and an X-Request-Id header on every POST, PUT and PATCH is documented for idempotent retries (10 of 15). No SLA, and the Platform Policy disclaims reliability and availability (0). The booking APIs are not marked beta or preview (10). Total 35. - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 61: No OpenAPI file. The public Postman collection of 87 requests can be downloaded as JSON from the documenter and carries request shapes and example responses (15 of 25). No llms.txt or Markdown copies for agents (0). Long descriptions with use cases that say which API fits which job, such as Consumer API for affiliates and restaurant websites and In-House for voice AI, and which booking links each partner type may use (15). Field tables give types and say which fields are required, with some enumerations such as table attributes, but much is prose (10). Example requests and responses, plus common-error tables naming business-rule codes per endpoint (13). Versioned paths (v1, v2, v3) and a change log section, though only one entry carries a date (8 of 15). Total 61. - Agent ergonomics 69: Availability takes a party size, a start time and forward and backward windows up to 720 minutes, and experiences are opt-in. Guest lists take limit (up to 2,000) and offset. No field selection (15). Pagination with hasNextPage and nextPageUrl on sync endpoints, filters such as updated_after (15). Error tables pair HTTP codes with named reasons like DinerHasOverlappingReservations and NotFarEnoughInAdvance (16). X-Request-Id gives idempotent writes, and slot locks can be released with DELETE (18). A booking takes three calls (search, lock, make) and there are no SDKs (5). Total 69. - Security & auth 33: OAuth 2.0 client credentials per partner, with the secret in the Authorization header and rotation on OpenTable's request. No scopes are documented for the client credentials grant, so the token's reach is set by the partner's agreement (20). Credentials are issued per API and per partner, and restaurants opt in through the onboarding flow, but no read-only token was found (8). Responses carry diner notes, special-relationship notes and reviews written by people, with no injection guidance (3). No audit log or per-call view for partners was found (0). TLS 1.3 only from 6 October 2025. www.opentable.com did not answer, so security.txt and any disclosure programme were unchecked, and no SOC 2 or ISO 27001 statement was found in the docs (2). Total 33. - Payments & pricing 5: No x402, MPP or L402 (0). No API prices published. Terms are set in each partner's agreement (0). A sandbox is granted after the application is approved, with no card mentioned, which gives part of the line (5 of 20). A person applies through a form and waits for review (0). Total 5. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 5: The change log has three undated entries (Spreedly support in Booking API v2, Stripe details for backward-compatible bookings, service fees) and one dated notice, TLS 1.3 only from 6 October 2025. The newest dated change is over 180 days old (0). Fewer than three dated changes in 90 days (0). Support runs through each partner's OpenTable representative, and the Platform Policy says OpenTable has no obligation to provide support (5 of 15). No official SDKs (0). No package to assess (0). Total 5. - Transparency & trust 42: Closed service. The Platform Policy is public, but the partner agreement it relies on is not, and the terms page linked from the docs could not be read because www.opentable.com did not answer (10 of 30). The Platform Policy requires partners to protect data and limits its use to the agreement. The privacy policy was unread, so no retention periods were checked (5 of 30). Consumer API v1 has no scheduled deprecation date, while the policy allows changes with or without notice and says individual notices are not given (5 of 20). No subprocessor list or data locations found (0). Total 20. Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (16 items): https://www.anchorterminal.com/fixes/opentable.md (JSON https://www.anchorterminal.com/fixes/opentable.json) ### What we couldn't check - unchecked: www.opentable.com timed out on every request, so robots.txt, the terms and conditions, the privacy policy, security.txt, the become-a-partner page and the legal entity were not read - unchecked: status.opentable.com components and incident history, which load by script - Rate limits per endpoint, which the docs leave to each partner's representative - Whether OAuth client credentials can be limited to read-only or to one API family - Whether the Platform Policy's ban on using the APIs on behalf of third parties allows an agent booking for its own user, which depends on the partner agreement ### Sources - API documentation (Postman documenter): (seen 2026-10-14) - API documentation as JSON, including Platform Policy, environments, booking APIs and change log: (seen 2026-10-14) - status page (frame only, contents load by script): (seen 2026-10-14) - partner portal: (seen 2026-10-14) - RDAP record for opentable.com: (seen 2026-10-14) ## Who's behind it (provenance 64/100, checked 2026-10-14) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | not found | 0/20 | | Domain age | opentable.com, registered 1999-01-17 (27 years) | 15/15 | | Endpoint on the vendor's domain | platform.opentable.com | 15/15 | | Terms of service | published, but our reader couldn't read it | 7/10 | | Privacy policy | published, but our reader couldn't read it | 7/10 | | Status page | status.opentable.com | 10/10 | | Changelog | published | 10/10 | | security.txt | could not be fetched | 0/10 | The terms and privacy URLs are the ones the API documentation links. www.opentable.com timed out on every request from our network on 14 October 2026, including robots.txt, so neither page nor the legal entity was read. The API's own Platform Policy (last updated 20 December 2024) is published at the top of docs.opentable.com and refers to each partner's agreement with OpenTable. status.opentable.com is a StatusDashboard page whose components and history load by script and were not readable to our reader. The change log is a section of the documentation (API Reference, Change Log), not a separate page. security.txt could not be fetched because www.opentable.com did not answer. RDAP gives opentable.com a registration date of 1999-01-17. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.opentable.com/legal/terms-and-conditions), read 2026-10-14. Our reader couldn't read it (no answer (stream error: stream ID 3; INTERNAL_ERROR; received from peer)). **Privacy policy** (https://www.opentable.com/legal/privacy-policy), read 2026-10-14. Our reader couldn't read it (no answer (stream error: stream ID 5; INTERNAL_ERROR; received from peer)). ## Live (updated 2026-10-14 09:42 UTC) - Right now: up, HTTP 200, 476 ms, checked 2026-10-14 09:42 UTC (get on `https://platform.opentable.com`) - Uptime 24h 100.0% (17 probes) · 30 days 100.0% (17 probes) · p50 545 ms · p95 3 s - Vendor status page: unknown, no machine-readable status found - Always current: https://www.anchorterminal.com/api/v1/live/opentable.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Strengths - Diner-side Consumer API v2 and venue-side In-House Booking API both cover availability, slot lock, booking, change and cancellation - Booking and cancellation policy endpoints return deposits, holds and cut-off rules before a booking is made - X-Request-Id on POST, PUT and PATCH requests makes retries safe - Error tables name business-rule failures such as DinerHasOverlappingReservations with their HTTP codes - A sandbox environment with its own OAuth host is granted after approval ## Weaknesses - Access needs an application, review by the partnerships team and an agreement, with no self-serve credentials - Rate limits are not published and come from the OpenTable representative - No OpenAPI file, llms.txt or SDK, only a Postman collection - The change log has one dated entry, the TLS 1.3 notice of 6 October 2025 - The Platform Policy allows API changes and suspension with or without notice and promises no support ## Before you call it (notes for agents) 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 First request: ```bash curl "https://oauth-pp.opentable.com/api/v2/oauth/token?grant_type=client_credentials" -H "Authorization: Basic BASE64_CLIENT_ID_AND_SECRET" ``` Through letme (picks today, calling later): https://letme.dev/opentable. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Eat App Partner API | D | 53.4 | 752 | booking.reservations, booking.availability, booking.venue, crm.records | no | https://www.anchorterminal.com/tools/eat-app.md | | TheFork B2B API | E | 43.6 | 951 | booking.reservations, booking.availability, booking.venue, crm.records | no | https://www.anchorterminal.com/tools/thefork.md | | SevenRooms | F | 17.7 | 1043 | booking.venue, booking.reservations, booking.availability, crm.records | no | https://www.anchorterminal.com/tools/sevenrooms.md | | TableCheck API | C | 57.1 | 661 | booking.availability, booking.reservations, booking.venue | no | https://www.anchorterminal.com/tools/tablecheck.md | | Resy | F | 10.3 | 1068 | booking.reservations, booking.availability, booking.venue | no | https://www.anchorterminal.com/tools/resy.md | | Square Appointments (Bookings API) | B | 68.1 | 242 | booking.availability, booking.venue | no | https://www.anchorterminal.com/tools/square-appointments.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The documentation is a public Postman collection of 87 requests covering booking, CRM, directory, menus, POS, private dining, reviews, sync tiers and profile content (source: ) - The Online Booking API (Consumer API v2) books for diners. Availability search, a slot lock that expires within 5 minutes, then make, modify or cancel the reservation (source: ) - The In-House Booking API books into a restaurant's own inventory and was built for voice AI reservation systems. It cannot change or cancel experience reservations (source: ) - All POST, PUT and PATCH requests should carry a unique X-Request-Id header so a retry is processed once (source: ) - Rate limits apply and vary by endpoint, and the numbers come from the partner's OpenTable representative (source: ) - The Platform Policy, last updated 20 December 2024, forbids using the APIs on behalf of third parties unless the partner's terms allow it, and forbids publishing uptime, response time or benchmark figures (source: ) - Card-guaranteed bookings use Spreedly tokenisation in Consumer API v2, with Stripe kept for backward-compatible bookings. Consumer API v1 has no scheduled deprecation date (source: ) - #5 of 9 in Best restaurant reservation and local appointment APIs for AI agents: https://www.anchorterminal.com/best/local-bookings/index.md - All 36 bookings comparisons: https://www.anchorterminal.com/compare/local-bookings/index.md ## Compare - [Chope vs OpenTable APIs](https://www.anchorterminal.com/compare/chope-vs-opentable.md): F 13.3 vs E 38.6 - [Eat App Partner API vs OpenTable APIs](https://www.anchorterminal.com/compare/eat-app-vs-opentable.md): D 53.4 vs E 38.6 - [OpenTable APIs vs Tock](https://www.anchorterminal.com/compare/opentable-vs-tock.md): E 38.6 vs F 12.4 - [OpenTable APIs vs Resy](https://www.anchorterminal.com/compare/opentable-vs-resy.md): E 38.6 vs F 10.3 - [OpenTable APIs vs SevenRooms](https://www.anchorterminal.com/compare/opentable-vs-sevenrooms.md): E 38.6 vs F 17.7 - [OpenTable APIs vs Square Appointments (Bookings API)](https://www.anchorterminal.com/compare/opentable-vs-square-appointments.md): E 38.6 vs B 68.1 - [OpenTable APIs vs TableCheck API](https://www.anchorterminal.com/compare/opentable-vs-tablecheck.md): E 38.6 vs C 57.1 - [OpenTable APIs vs TheFork B2B API](https://www.anchorterminal.com/compare/opentable-vs-thefork.md): E 38.6 vs E 43.6 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on opentable.com or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "opentable", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html OpenTable APIs on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![OpenTable APIs on Anchor Terminal](https://www.anchorterminal.com/badges/opentable.svg)](https://www.anchorterminal.com/tools/opentable) ``` Plain link: ```html OpenTable APIs on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say OpenTable APIs is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/opentable-dark.png - Light: https://www.anchorterminal.com/assets/share/opentable-light.png - Create a video and download its frames: https://www.anchorterminal.com/assets/listing-video/index.html?listing=opentable