Connect OpenTable
Connecting OpenTable mirrors your Rex bookings onto your OpenTable book. A guest reserves through Rex, and the same reservation appears in OpenTable against your restaurant — so your front-of-house team works from one book instead of checking two systems.
The sync runs one way only: Rex to OpenTable. Reservations booked directly in OpenTable do not appear in Rex, and Rex does not read availability from OpenTable.
Before you start
OpenTable is a plan feature. If no OpenTable card appears in your integration settings, your plan does not include it — check Billing & Plan or contact Rex support.
You also need your venue's OpenTable Restaurant ID, usually called the RID. It tells Rex which OpenTable restaurant your bookings belong to.
Where it's configured
OpenTable is set up in two places. The API connection is entered once for the whole account. Each venue is then switched on individually with its own RID, so you can run OpenTable at one location and not another.
Enter the account-level connection
Open Integrations from the Marketplace group in the sidebar and find the OpenTable card. The four values here connect Rex to the OpenTable API for every venue in the account.
| Field | Description |
|---|---|
| Client ID | The client identifier for your OpenTable API credentials. |
| Client Secret | The matching secret. Treat it like a password. |
| OAuth URL | The OpenTable endpoint Rex exchanges the credentials at for an access token. |
| API URL | The OpenTable booking API endpoint Rex sends reservations to. |
OpenTable issues these values. If the card is empty and you do not have them, contact Rex support rather than guessing — a wrong endpoint fails silently.
Turn OpenTable on for a venue
Open the venue and stay on its General tab. Scroll to the Integrations section, find the OpenTable card, and open its settings.
Set both fields, then save:
| Field | Description |
|---|---|
| Enable OpenTable Integration | Turns the sync on for this venue. |
| OpenTable Restaurant ID (RID) | The OpenTable restaurant these bookings belong to. |
Both are required. If the toggle is on but the RID is blank, Rex skips the sync entirely and writes nothing to OpenTable — with no error shown anywhere.
Book a test reservation
Make one real booking on your reservation page and check it appears on your OpenTable book with the right party size and start time. Then cancel it and confirm the cancellation lands in OpenTable too.
What syncs, and when
Rex pushes to OpenTable at three moments in a reservation's life. Each push is triggered by the booking itself — there is no schedule and no manual sync button.
| Field | Description |
|---|---|
| New booking | Rex holds the slot in OpenTable, creates the reservation, and stores the OpenTable confirmation number against it. |
| Modified booking | Party size, date and time, and the special request are updated on the existing OpenTable reservation. |
| Cancelled booking | The OpenTable reservation is cancelled. |
Modifications and cancellations depend on the original booking having synced. Rex matches them using the OpenTable confirmation number it saved at creation, so if that first sync failed, later changes to the same reservation are skipped.
What Rex sends
Each OpenTable reservation is created with:
- The guest's first name, last name, email address and phone number.
- The party size, and the start time in the venue's time zone.
- A special request built from the booking — the package name, then the guest's notes if they left any, prefixed with [Rex] so staff can see where it came from. OpenTable caps this field, so long notes are trimmed.
- The guest's marketing opt-in, passed through from whether they chose to receive offers at checkout.
The [Rex] prefix and package name are what make a Rex booking recognisable on the OpenTable book. Keep package names short enough to read at a glance.
What your guests see
Once a venue has OpenTable enabled, an OpenTable notice appears on the payment step of that venue's reservation page, alongside the OpenTable logo:
Powered by OpenTable. By clicking Complete Reservation, you agree to the OpenTable Terms of Use and Privacy Policy.
Both policy names link out to OpenTable. The notice is required by OpenTable and appears automatically — there is no setting to hide it, and it disappears if you turn the integration off.
Check that a sync worked
Every attempt is recorded in the venue's integration sync history, whether it succeeded or failed. Look for these entries:
| Field | Description |
|---|---|
| Sync with OpenTable | The reservation was created in OpenTable. |
| Update Sync with OpenTable | A change to the reservation was pushed. |
| Cancel Sync with OpenTable | The cancellation was pushed. |
Troubleshooting
Nothing appears in OpenTable
Check the venue first. Enable OpenTable Integration must be on and OpenTable Restaurant ID (RID) must be filled in — Rex skips the sync when either is missing, and it does so quietly. Then check that the account-level card still holds all four connection values.
New bookings sync, changes do not
That reservation's original sync did not succeed, so Rex has no OpenTable confirmation number to update against. Check its sync history for a failed Sync with OpenTable entry.
Bookings land at the wrong time
Rex sends the start time in the venue's time zone. Confirm the venue's time zone is correct in its general settings, and that the OpenTable restaurant uses the same zone.
Sync entries show as failed
Usually the credentials or the RID. A wrong Client ID, Client Secret, OAuth URL or API URL fails at the token step. A RID that does not match your OpenTable restaurant fails at the booking step.
Updated Aug 25, 2026
Was this helpful?