OpenTable | Tooluse.net Help

Official Consumer API v2 for approved OpenTable partners. Search availability, dining areas and experiences using partner client credentials. This is not personal account OAuth. Complete reservations through the visible OpenTable booking flow.

What you can do (3)

What you can do

Available commands: 3 (3 read, 0 write). Enable only the commands your application needs.

Command	Effect
Find OpenTable availability — `opentable.availability.search`	Read
Read OpenTable dining areas — `opentable.availability.metadata`	Read
List OpenTable dining experiences — `opentable.experiences.list`	Read

Connect and use

Open the integration's connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.

Get your provider credentials

Follow these steps for OpenTable, then enter the issued values in the connection form below.

Request OpenTable partner API access through the official developer guide. With approval, enter the partner client ID and client secret, or an existing partner access token, and select the matching production or development environment. Save the connection and enable availability, dining-area or experience reads. Personal OpenTable sign-in does not provide these credentials; complete bookings on OpenTable.

Official credential setup

Where to enter credentials

In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.

Connection field	Requirement
OpenTable partner client ID	Optional
OpenTable partner client secret	Optional
Existing partner access token	Optional
Environment: production or development	Optional

Open API keys and create a Tooluse.net key for the enabled commands.

Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.

Configure Claude Code, Codex or Cursor once

Permissions and results

If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.

Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.

Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.

Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.

Call from your client

Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.

Configure Claude Code, Codex or Cursor once

Discover your enabled tools

List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.

curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"

Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.

HTTP call

curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {
    "restaurantId": 1074796,
    "startDateTime": "2026-11-05T19:00",
    "partySize": 2
  }
}'

Commands

Find OpenTable availability — opentable.availability.search

Run Find OpenTable availability with OpenTable. This is a read command; it does not grant access beyond the connected account's permissions.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter	Type	Required in parent	Description	Constraints
`restaurantId`	integer	Required	Restaurant ID	`minimum: 1; maximum: 2147483647`
`startDateTime`	string	Required	Restaurant local date and time	`pattern: "^\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}$"`
`partySize`	integer	Required	Party size	`minimum: 1; maximum: 20`
`forwardMinutes`	integer	Optional	Minutes after requested time	`minimum: 0; maximum: 120`
`backwardMinutes`	integer	Optional	Minutes before requested time	`minimum: 0; maximum: 120`
`includeExperiences`	boolean	Optional	Include dining experiences

Full JSON Schema

Full JSON Schema

Example input

{
  "restaurantId": 1074796,
  "startDateTime": "2026-11-05T19:00",
  "partySize": 2
}

At most 2 provider requests per invocation; timeout: 30 seconds.

Read OpenTable dining areas — opentable.availability.metadata

Run Read OpenTable dining areas with OpenTable. This is a read command; it does not grant access beyond the connected account's permissions.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Parameter	Type	Required in parent	Description	Constraints
`restaurantId`	integer	Required	Restaurant ID	`minimum: 1; maximum: 2147483647`

Full JSON Schema

Full JSON Schema

Example input

{
  "restaurantId": 1074796
}

At most 2 provider requests per invocation; timeout: 30 seconds.

List OpenTable dining experiences — opentable.experiences.list

Run List OpenTable dining experiences with OpenTable. This is a read command; it does not grant access beyond the connected account's permissions.

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Parameter	Type	Required in parent	Description	Constraints
`restaurantId`	integer	Required	Restaurant ID	`minimum: 1; maximum: 2147483647`

Full JSON Schema

Full JSON Schema

Example input

{
  "restaurantId": 1074796
}

At most 2 provider requests per invocation; timeout: 30 seconds.

Errors

Check the key's expiry, revocation, workspace and allowed operations.

Reuse the same idempotency key only for the same request.

The connection or provider limit has been reached. Check the receipt before retrying.

Test the connection

Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.

Official provider documentation