OpenTable Partner API: How to Get Access (and What It Doesn't Cover)

OpenTable has no public API.
There's no developer portal where you sign up, verify your email, and start making calls.
Every official integration runs through the OpenTable partner API program, and the documentation follows the agreement rather than preceding it.
You commit first, read second.
If you're a developer who just needs restaurant data (availability, reviews, menus, ratings), that's a frustrating loop.
This guide maps what the partner programs actually cover, who gets in, what the InstantBook searches are really about, and the route that works without a partnership.

Key Takeaways

• OpenTable's APIs are partner-gated. Restaurant software integrations and booking-partner programs exist, and both require a commercial relationship before you see documentation.
• A "developer key signup" doesn't exist. The application is for a partnership, and data-only use cases generally don't qualify.
• The wall is familiar. It's the same partner-gate pattern hotel platforms use, the one we documented for the Booking.com API.
• InstantBook is mostly a vocabulary mix-up. The term is Airbnb's, but the intent behind those searches (instantly confirmable, machine-readable reservations) maps to real OpenTable behavior.
• Restaurant data has an open route. Third-party data APIs cover OpenTable search, details, reviews, menus, and availability slots as structured JSON, no partnership required.

Does OpenTable Have an API?

Yes, but not for you to sign up for.
OpenTable's APIs exist for two kinds of partners: restaurant-side software (POS systems, guest management tools integrating with OpenTable's restaurant platform) and booking partners (products that surface OpenTable reservations inside their own apps).
Both routes involve an application, a business case, and an agreement before any documentation changes hands.
What doesn't exist is a general-purpose data API: no public endpoint for searching restaurants, reading reviews, or pulling menus.
That's the short answer.
The rest of this guide is what to do with it.

The Official OpenTable Partner APIs

The restaurant-side route is the deepest one.
Software that serves restaurants (point of sale, CRM, guest messaging) can integrate with OpenTable's restaurant management platform to sync reservations and guest data for shared customers.
The scope ends at restaurants that are your clients.
The booking-partner route is what most people imagine when they picture an OpenTable API: search restaurants, show availability, book a table, all inside your app.
Those integrations exist for established consumer platforms, under commercial terms, typically negotiated case by case.
Both programs share the trait that matters here: the data they expose is scoped to the partnership, and market-wide read access isn't part of either.
If your product needs to know every bookable slot in a city tonight, or the review score of 200 restaurants in a comp set, neither program is designed to answer.

What Is OpenTable InstantBook?

A surprising slice of search traffic pairs OpenTable with "InstantBook", so let's untangle it.
InstantBook is an Airbnb feature name.
It means a booking that confirms immediately, with no host approval step.
OpenTable has no feature by that name, and the searches almost certainly borrow the vocabulary.
The intent behind them is real, though, and increasingly it comes from people building AI agents.
The question being asked is: can a reservation be confirmed instantly and programmatically, without a phone call or a request-and-wait loop?
On OpenTable, standard reservations already confirm instantly: an open slot is bookable, and booking it doesn't wait on the restaurant's approval.
What an agent builder needs on top of that is machine-readable availability, which slots exist for a given party size, date, and time, before sending anyone to book.
That part is a data problem, and it's solvable today.
Availability and time-slot data is exactly the kind of surface a restaurant data API exposes, and for agent builds specifically, the OpenTable MCP server makes those lookups available to AI agents directly.
The reservation itself still happens on OpenTable.

What Official Access Doesn't Give You

Mapping the need to the reality:

Menus deserve a note because the searches for an OpenTable menu API are persistent.
Restaurants publish structured menus on their OpenTable profiles (names, sections, items, prices), and that data is readable through the data-API route below, including the awkward realities like prices published as "MKT" instead of a number.
Reviews are similar: diner ratings and review counts are public on every profile, with no official way to read them programmatically.

Getting OpenTable Data Without a Partnership

Third-party data providers maintain extraction infrastructure against OpenTable's public surfaces and publish documented endpoints anyone can use.
The OpenTable API from StayAPI covers eight of them: restaurant search by coordinates, details, reviews, menus, availability, time slots, private dining, and URL-to-ID conversion.
Here's a real search for restaurants near downtown San Francisco:

curl -X GET "https://api.stayapi.com/v1/opentable/search?latitude=37.7749&longitude=-122.4194&party_size=2" \
  -H "x-api-key: YOUR_API_KEY"

The response (truncated):

{
  "success": true,
  "restaurants": [
    {
      "id": 1002775,
      "name": "Hardwood Bar & Smokery",
      "primary_cuisine": "Barbecue",
      "price_band": { "name": "$30 and under" },
      "rating": 4.7,
      "review_count": 112,
      "neighborhood": "SOMA",
      ...
    }
  ],
  "total": 377
}

From that id, the menu endpoint returns the restaurant's full published menus (this one carries 2 menus, 11 sections, and 68 priced items), and the availability endpoints return bookable slots for a date, time, and party size.
The full parameter reference is in the OpenTable search endpoint documentation.
There are no rate limits, and responses are real-time: a request returns the restaurant's current state, not a cached snapshot.
For one-off lookups before writing any code, the free explorer tool below returns the same data from a pasted OpenTable URL.

Getting Started

1. Sign up at stayapi.com. Free tier, no credit card, no partner agreement.
2. Preview the data with the free OpenTable explorer: paste any restaurant's OpenTable URL and see its structured data.
3. Resolve your restaurants. Search by coordinates as above, or convert restaurant page URLs to IDs with the URL-to-ID endpoint.
4. Pull the surfaces you need per restaurant: details, reviews, menus, or availability slots.
5. Pipe the JSON into your stack: database, Google Sheets, Looker Studio, Power BI, or no-code platforms like N8N and Make.com. For AI agent builds, point your agent at the MCP server instead. For projects covering whole markets, book a demo call.

FAQ

Does OpenTable have a public API?

No.
Official APIs exist for restaurant-software partners and booking partners, both under commercial agreements.
For read access to restaurant data (search, reviews, menus, availability), third-party data APIs are the open route.

How do I get an OpenTable API key?

Officially, by becoming a partner: restaurant-platform integrations for software vendors, or booking partnerships for consumer apps.
There's no self-serve developer key.
Data APIs issue keys on signup, which covers the read-access use cases the official programs don't.

What is OpenTable InstantBook?

The name is borrowed from Airbnb, where it means instantly confirmed bookings.
OpenTable reservations already confirm instantly when a slot is open, so the practical version of the question is about reading availability programmatically, which is a data-API capability.

Is there an OpenTable menu API?

No official one.
Restaurants publish structured menus on their profiles, and data APIs expose them as JSON: menu names, sections, items, and prices, including nonnumeric prices like "MKT".

Can I get OpenTable reviews through an API?

Diner ratings and review counts are public on every restaurant profile, and a data API returns them as structured fields (rating out of 5, review count, and review content).
Any restaurant on the platform works, so comp-set monitoring is as available as tracking your own.