OpenTable
OpenTable is a global restaurant reservation platform owned by Booking Holdings. The OpenTable Partner Portal exposes restricted partner APIs for reservations, availability, restaurant content, reviews, and CRM integrations to approved partners.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles OpenTable the way a machine reads it — 16 machine-readable artifacts across 2 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — OpenTable scores 23.2/100 (emerging), with a separate agent-readiness read of 7/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile OpenTable
Each block below is one kind of artifact we hold for OpenTable. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 2
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
OpenTable Partner API
Restricted REST API for approved partners covering restaurant content, availability, reservations, and CRM. Access is granted through the OpenTable Partner Portal under contract...
OpenTable Affiliate / Restaurant Search Widgets
Widget and reservation embeds for affiliate sites, plus restaurant search/availability for approved partners.
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Opentable Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Opentable Finops
FINOPSFeatures 4
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Restaurant Content and Directory
Programmatic access to restaurant profiles, locations, and metadata for approved partners.
Availability and Reservations
Real-time table availability lookups and reservation booking for partner experiences.
Reviews and Guest Data
Access to diner reviews and guest/CRM data for approved integrations under contract.
Sandbox Environment
Approved partners receive a sandbox for discovery and testing before production access.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Use Cases 3
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Embedded Restaurant Booking
Third-party apps and sites embed availability and booking flows to let diners reserve tables without leaving the partner experience.
Tech Stack Integration
Restaurants connect OpenTable to POS, CRM, and operations systems to unify reservation and guest data.
Affiliate Referrals
Affiliate partners surface OpenTable availability and earn from referred reservations.
Integrations 3
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
POS Integrations
OpenTable integrates with point-of-sale systems to sync reservations, covers, and guest spend data with restaurant operations.
CRM and Marketing Platforms
Guest profile, reservation, and review data can flow to partner CRM and marketing tools through approved partner integrations.
Affiliate and Booking Widgets
Affiliate sites and third-party platforms embed OpenTable reservation widgets and deep links to surface real-time availability and drive bookings.
Resources
Every other property we hold for OpenTable — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Build 6
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/opentable · machine-readable index on apis.io