OpenTable connector
Connect OpenTable to Silux Chat with a read-only connection for appointments and bookings. It is tested with a real call when you connect it and re-checked every day.
Good to know: Partner-only API (OpenTable approval required). Reservations are found by the guest's UK mobile number — OpenTable has no email lookup.
What your bot can do with OpenTable
Appointments and bookings
Reads upcoming and recent appointments or reservations from OpenTable — date and time, service and status.
Customers ask: “When is my next appointment?” · “Is my booking confirmed?”
Connected and tested when you connect OpenTable, but the bot does not answer customers from it: OpenTable can’t prove who is asking, and these records are personal. Email support@siluxcall.co.uk to discuss using it.
Set it up
Most businesses finish in under ten minutes. You need to be able to sign in to OpenTable as an administrator to create the key.
Step 1 — in OpenTable
OpenTable must approve Silux Chat as a partner for your restaurant; then enter your restaurant ID.
Least access: grant only the read permissions named above (customers, orders, invoices, bookings or tickets — whichever this connector uses). Never use an owner or full-admin key where OpenTable lets you create a restricted one.
Step 2 — in Silux Chat
- 1Open Dashboard → Integrations → Connectors and search for “OpenTable”.
- 2Fill in:
Field Example Stored Restaurant ID (rid) 123456 Setting Client ID •••••••• Encrypted Client secret •••••••• Encrypted - 3Press Connect & test. The platform makes a real, read-only call to OpenTable with a made-up customer and shows a tick or a cross for each capability, with OpenTable’s exact error if something is refused.
You create an API client in OpenTable and paste its client ID and secret. The platform exchanges them for short-lived access tokens automatically, so nothing needs renewing by hand.
How customer verification works
OpenTable holds no customer records that the platform can match by name and email, so this connector cannot verify customers by itself. It is tested when you connect it and re-checked every day. To plan how its data should reach your customers alongside your verification route — a connector that can look customers up, or your own Account Connect endpoints — email support@siluxcall.co.uk.
What the bot can and cannot see
Can see (after verification)
Nothing — see the verification section above.
Only these standard fields are mapped from OpenTable’s responses. Everything else in the response is discarded before the bot sees it.
Never sees
- passwords, security answers or login details
- records belonging to anyone other than the verified customer
- anything outside the fields listed alongside
Security
Keys encrypted at rest
Credentials are stored encrypted, shown only masked after saving, and destroyed — not just hidden — when you disconnect.
Read-only look-ups
Every capability is a look-up. The connector cannot create, change or delete anything in OpenTable.
HTTPS only
Calls go to the vendor’s HTTPS address, redirects are not followed, and private network addresses are refused.
Injection-safe
Values a customer types are cleaned before they are placed in OpenTable’s search, and URL-encoded in addresses.
Other customers filtered out
A row that names a different customer’s email is dropped, whatever the vendor’s search returned.
Checked daily
Connections are re-tested every day, and the owner is emailed if a working connection starts failing.
More: Security & data protection.
Technical details
For developers and IT teams: the OpenTable endpoints this connector reads, relative to https://platform.opentable.com. Values in braces come from the settings you enter.
| Capability | Request | Standard fields returned |
|---|---|---|
| Appointments and bookings | POST/inhouse/v1/booking/{rid}/reservations/search | id, start, status, party_size |
Test level: Documented-API tested. Each capability is run automatically against OpenTable’s documented example responses and must produce the standard fields; your own connection is then tested with a real call when you connect. The bot receives these through the standard Account Connect endpoints, exactly as if you had built them yourself.
Troubleshooting
| What you see | Likely cause and fix |
|---|---|
| “the vendor refused the credentials (401)” or (403) | The key was revoked, has expired or was copied incompletely, or it lacks a read permission this connector needs. Create a fresh read-only key in OpenTable and reconnect. |
| “That Restaurant ID (rid) doesn’t look right” | Enter it in the form shown, e.g. 123456 — without https:// or a trailing slash. |
| Customers are “not matched” although they exist | Customers are looked up by email or mobile, not postcode. Check the customer’s email or mobile is saved on their OpenTable record, and that the surname matches. |
| A capability shows a cross but others work | That permission wasn’t granted in OpenTable, or your OpenTable plan doesn’t include that part of the API. Grant it and press Test. |
| “the vendor kept rate-limiting the request” | OpenTable returned “too many requests” three times in a row. The platform already waits and retries automatically (up to 10 seconds, as OpenTable asks); if it persists, ask OpenTable about your API quota. |
| Results are empty for a verified customer | The records exist under a different email or customer record in OpenTable, or none are recent. Check the customer’s record in OpenTable directly. |
Full error reference: Troubleshooting & error reference.
Frequently asked questions
Is the OpenTable connection read-only?
Yes. Every request Silux Chat makes to OpenTable is a look-up (a few vendors use POST for searches); none creates, changes or deletes anything in OpenTable. Give the key or sign-in read-only permissions wherever OpenTable offers them.
Do I need a developer to connect OpenTable?
No. You paste the details listed in the set-up steps in Dashboard → Integrations → Connectors and press “Connect & test”. The platform makes a real call to OpenTable straight away and shows exactly which features work.
How does the bot know it is really my customer?
OpenTable holds no customer records the platform can search, so it cannot verify customers by itself. See the verification section on this page, or email support@siluxcall.co.uk to plan the right set-up.
What happens if my OpenTable key is revoked or expires?
The bot tells customers it can’t check their account right now — it never pretends there are “no orders”. Connections are re-tested daily and the account owner is emailed when a working connection starts failing. Reconnect it in Dashboard → Integrations → Connectors.
How has the OpenTable connector been tested?
It is Documented-API tested: every capability is run automatically against OpenTable’s documented example responses and must produce the standard fields. When you connect, it is tested again with a real call to your own OpenTable account before your bot uses it.
Other hospitality connectors
Need help with your integration?
Our integration team can review your endpoints, help you choose the right connector and check a test run with you. Tell us which system you use and what you would like the bot to answer.