OpenTable API Documentation

Name: OpenTable API Documentation API
Brand: OpenTable API Documentation
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceOrder Managementoauth248 EndpointsREST

For Agents

Check restaurant availability, lock slots, and create or modify reservations on OpenTable on behalf of approved partners.

Quickstart

Get started with OpenTable API Documentation in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"book a restaurant reservation"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with OpenTable API Documentation API.

Check availability for a single OpenTable restaurant by RID and party size

Lock a reservation slot before booking using POST /v2/booking/{rid}/slot_locks

Create a reservation with POST /v2/booking/{rid}/reservations

Modify or cancel an existing reservation by RID and confirmation ID

GET STARTED

Start building with OpenTable API Documentation API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for OpenTable API Documentation, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for OpenTable API Documentation, keeping it validated and agent-ready. The OpenTable Partner API gives approved integration partners programmatic access to restaurant availability, reservations, slot locks, booking and cancellation policies, CRM guest records, and partner sync feeds. It is OAuth 2.0 protected and gated by partner approval, with sandbox and production environments. Capabilities span checking availability for a restaurant, locking a slot, creating or modifying reservations, managing guest profiles and tags, and exchanging POS data and menu webhooks.

Use Cases

Patterns agents use OpenTable API Documentation API for, with concrete tasks.

★ Concierge Reservation Booking

A concierge or hotel platform integrates OpenTable to book tables on behalf of guests. The flow calls /v2/availability/{rid3} to find open slots, /v2/booking/{rid}/slot_locks to hold a slot during checkout, then /v2/booking/{rid}/reservations to confirm. Booking and cancellation policies retrieved from /v2/booking-policies and /v2/cancellation-policies are surfaced to the guest before commit.

Call GET /v2/availability/{rid3} for a target rid, lock a slot via POST /v2/booking/{rid}/slot_locks, then create the reservation with POST /v2/booking/{rid}/reservations

Guest CRM Synchronisation

Restaurant groups maintaining a unified CRM can push guest profile updates, tags, photos, loyalty levels, and insights into OpenTable through the /api/v3/external/partners/{partner-id}/restaurants/{rid}/guests endpoints. This keeps host stand staff informed on arrival and ensures preferences flow back into the central CRM after each visit. Photo upload, tag assign, and insight update endpoints are all PUT or POST operations keyed by guest-id.

PUT /api/v3/external/partners/{partner-id}/restaurants/{rid}/guests/{guest-id}/tags with the partner-id, rid, guest-id, and tag payload to apply a 'VIP' tag

Reservation Modification and Cancellation

Customer service platforms handling restaurant booking changes can modify reservations via PUT /v2/booking/{rid}/reservations/{rid}-{confirmation-id} and cancel via DELETE /inhouse/v1/booking/{rid}/reservations/{confirmation-id}. The /v2/cancellation-policies/{rid}/{cancelationid} endpoint exposes the applicable fee or no-show rules so the agent can warn the guest before issuing the cancellation.

Fetch /v2/cancellation-policies/{rid}/{cancelationid}, present the fee, then DELETE /inhouse/v1/booking/{rid}/reservations/{confirmation-id} to cancel

AI Agent Restaurant Assistant

An AI agent helping a user 'find and book a steakhouse for 4 tonight' can use OpenTable through Jentic without manually negotiating OAuth flows. Jentic resolves the natural-language intent into the right /v2/availability and /v2/booking/{rid}/reservations calls, supplies partner credentials from the vault, and returns the confirmation number for the agent to relay to the user.

Through Jentic, search 'book a restaurant reservation', resolve to POST /v2/booking/{rid}/reservations, and execute with party size, date, and time

Key Endpoints

48 endpoints — jentic publishes the only available openapi specification for opentable api documentation, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/v2/availability/{rid3}

Get open availability for a restaurant

POST

/v2/booking/{rid}/slot_locks

Lock a reservation slot

POST

/v2/booking/{rid}/reservations

Create a reservation

PUT

/v2/booking/{rid}/reservations/{rid}-{confirmation-id}

Modify an existing reservation

GET

/v2/booking/{rid}/reservations/{rid}-{confirmation-id}

Retrieve a reservation

GET

/v2/cancellation-policies/{rid}/{cancelationid}

Fetch the cancellation policy

POST

/api/v3/external/partners/{partner-id}/restaurants/{rid}/guests

Create a CRM guest record

GET

/api/v2/oauth/token

Obtain an OAuth access token

GET

/v2/availability/{rid3}

Get open availability for a restaurant

POST

/v2/booking/{rid}/slot_locks

Lock a reservation slot

POST

/v2/booking/{rid}/reservations

Create a reservation

PUT

/v2/booking/{rid}/reservations/{rid}-{confirmation-id}

Modify an existing reservation

GET

/v2/booking/{rid}/reservations/{rid}-{confirmation-id}

Retrieve a reservation

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

OpenTable OAuth client credentials and refresh tokens are stored encrypted in the Jentic vault. Agents call OpenTable through Jentic without seeing the raw secret, and tokens are refreshed centrally without redeploying agent code.

Intent-based discovery

Agents search Jentic with intents like 'book a restaurant reservation' or 'lock a table slot' and Jentic returns the matching OpenTable operation with its parameter schema.

Time to first call

Direct OpenTable integration: 1-2 weeks including OAuth flow, sandbox testing, slot lock semantics, and partner approval. Through Jentic: under 1 hour once partner credentials are added to the vault.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Twilio API

Send SMS confirmations and reminders for OpenTable reservations created via the API.

Pair with OpenTable for reservation lifecycle messaging — confirmations, reminders, cancellations.

Complementary

Stripe API

Charge guests for prepaid reservations or no-show fees referenced in OpenTable policies.

Use Stripe alongside OpenTable when the booking includes a prepaid deposit or cancellation fee charge.

Complementary

SendGrid API

Send transactional reservation emails — confirmation, modification, cancellation receipts.

Pair with OpenTable when an email channel is required alongside the OpenTable transactional flow.

FAQs

Specific to using OpenTable API Documentation API through Jentic.

Why is there no official OpenAPI spec for OpenTable API Documentation?

OpenTable does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call OpenTable API Documentation via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the OpenTable API use?

OpenTable uses OAuth 2.0 — partners obtain an access token from /api/v2/oauth/token and pass it as a Bearer token on subsequent requests. Through Jentic, the client credentials are stored encrypted in the vault and the access token is refreshed automatically.

Can I book an OpenTable reservation with the OpenTable API without slot locking first?

OpenTable strongly recommends the lock-then-book pattern: POST /v2/booking/{rid}/slot_locks before POST /v2/booking/{rid}/reservations. The slot lock holds the inventory during the user's checkout step so concurrent requests don't double-book.

What are the rate limits for the OpenTable API?

OpenTable enforces partner-specific rate limits set during contracting and may revoke or throttle access at its discretion per the platform policy. Limits are documented in your partner onboarding materials. Subscribe to the OpenTable API Status Dashboard to receive notice of platform-wide limit changes.

How do I check restaurant availability through Jentic?

Search Jentic for 'check restaurant availability', load the GET /v2/availability/{rid3} schema, and execute with the restaurant ID, date, and party size. Jentic returns the open slot times and prices.

Is the OpenTable API free to access?

No — access requires a signed partner agreement with OpenTable. Apply via opentable.com/restaurant-solutions/api-partners. Pricing and tier eligibility are negotiated during contracting and depend on use case and integration scope.

Does the OpenTable API support iOS or Android client apps directly?

The API is REST/JSON over HTTPS and works from any client that can hold OAuth credentials, but OpenTable's policy restricts client-side credential storage. Mobile apps typically proxy through a partner backend that holds the OAuth client secret and forwards user actions.