{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/local-bookings.venue-data-sync/",
    "json": "https://www.anchorterminal.com/niches/local-bookings.venue-data-sync/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/local-bookings.venue-data-sync/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/local-bookings.venue-data-sync/index.min.md"
  },
  "markdown": "One company's docs show a full fit.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 1 | 4 | 31 | 10 | 4 |\n\n## What counts as done\n\nReservations or appointments and guest records read incrementally by modified date through the API and written to the target, with health and allergy fields left out unless the venue asks, resuming after a 429 without gaps.\n\nHow agents ask for it: pull all our TheFork reservations into the CRM; fill each report from today's appointments; which regulars haven't booked in three months\n\n## Does the job\n\nThe docs show it meets the test above, and nothing we read says otherwise.\n\n- **OpenTable APIs (OpenTable)**: Sync API v2 reservations and guests take updated_after with limit and offset paging, and reservation webhooks push new bookings, by restaurant id and tier.\n\n## Does the job, with a limit\n\nIt does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.\n\n- **Eat App Partner API (EAT APPLICATION DMCC)**: List Reservations and List Guests page at up to 100, with reservation and guest webhooks, but filters are by start date and status, not modified date.\n- **Square Appointments (Bookings API) (Block, Inc.)**: ListBookings filters by start time, not modified date; changes arrive as booking.created and booking.updated webhooks with seller-level access (acc-08 syncs appointments), but the rate limit is per application and unpublished.\n- **TableCheck API (TableCheck Inc.)**: GET reservations, Sync API webhooks and Feeds v1 batch export exist, but a modified-since filter was not confirmed on the pages read and keys are issued only by the API team.\n- **TheFork B2B API (La Fourchette SAS)**: Reservations list by updatedDate by default and customers by update date, with webhooks and 429 backoff, but acc-20 saw billAmount change shape without notice and stop the sync for 15,906 reservations.\n\n## Couldn't check\n\nThe docs were closed to us, or silent. These carry no mark either way.\n\n- **Resy (Resy Network, Inc.)**: No public venue API reference; only the integrations page and acc-10's report of venue keys.\n- **SevenRooms (SEVENROOMS LLC)**: CRM and POS integrations are advertised, but the API reference behind a provisioned login was not readable.\n- **Tock (Tock LLC)**: A Reservation, Patron and payment data model with a swagger file is published, but no endpoint, credential or filter is documented, so how a venue reads it is unknown.\n\n- not this job: Chope (The Chope Group Pte Ltd): No venue data API is documented on chope.co.\n- not this job: Treatwell (Treatwell Limited): No public venue data API is documented.\n\n## What stops agents finishing\n\n- response format changed without notice\n- no endpoint lists the venues a credential covers\n- per-application rate limit shared by every venue\n\n## Around it\n\nAfter: crm.upsert-contact, lifecycle-marketing.win-back, spreadsheets.write-table.\n\n## Where this comes from\n\nWeight 10 of 100 in Restaurant \u0026 local bookings: 4 of 30 counted accounts (TheFork CRM import, Square appointment reports, a multi-tenant Square app), rounded up from 9\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/local-bookings.venue-data-sync.json, or the MCP tool get_use_case with id local-bookings.venue-data-sync. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Sync a venue's bookings and guests into its other systems",
        "url": ""
      }
    ],
    "description": "Sync a venue's bookings and guests into its other systems: 1 companies fully do it, 4 with a limit, 31 carry the tag. Every listing in Restaurant \u0026 local bookings with the reason and a source.",
    "facts": null,
    "h1": "Sync a venue's bookings and guests into its other systems",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/local-bookings.venue-data-sync/",
    "published": "",
    "section": "agents",
    "title": "Sync a venue's bookings and guests into its other systems | Anchor…",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/local-bookings.venue-data-sync/"
  },
  "tokens": {
    "markdown": 1050,
    "slim": 280
  },
  "version": 1
}
