TheFork
Keeps menu highlights and prices fresh on your TheFork listing.
Simulated
What it does
- Keeps your menu link and headline dishes current in the booking journey
- Listed under Reservations & guests in your admin.
This connector runs in simulate mode.
Simulated — the connector runs the whole pipeline for real: it validates your credentials' shape, builds the exact payload it would send, counts the items and writes the result to your sync log. It just doesn't make the outbound call, because that system's transport isn't finished. Nothing is faked and nothing is hidden — the panel says so, the sync log says so, and this page says so. When the transport lands, the connector flips to Live and your configuration keeps working.
What it needs from you
| Field | Type | Looks like |
|---|---|---|
| API key | secret — write-only | — |
| Restaurant UUID | text | — |
Secrets are write-only: once saved, Carte never shows them again, and leaving a secret field blank when you save keeps the value you entered before.
Setting it up
- In your Carte admin, open Integrations and find TheFork under Reservations & guests.
- Enter API key, Restaurant UUID, then save.
- Press Test connection. It tells you plainly whether it reached TheFork or not.
- Press Sync to push your live menu. The result — item count and outcome — lands in your sync log either way.
Every attempt is logged.
Tests and syncs write to the sync log on your Integrations page, with the outcome and the item count. It is the first place to look when something goes quiet.