Tock
Tock is a Chicago-founded reservation, ticketed events, takeout, and delivery management platform for restaurants, wineries, and hospitality venues. Founded in 2014 by Nick Kokonas, Brian Fitzpatrick, and Grant Achatz to support prepaid and ticketed dining (originated at Alinea Group), Tock pioneered the prepaid reservation model and expanded into takeout, wine delivery, and experience ticketing through the pandemic. Squarespace acquired Tock for approximately $400 million in 2021, then sold it to American Express in June 2024 as part of Amex's strategy to deepen its dining and premium-experience footprint. Tock is operated as an Amex-owned property today and continues to serve restaurants globally through exploretock.com. Tock publishes API documentation and data-model specifications at api.exploretock.com covering its Reservation and Guest data models. Programmatic access is delivered through a Data Exports API (twice-daily reservation and guest exports), a Guest Profile Ingest API (create/update of basic guest information), and a real-time Reservation Webhook. API and webhook access is an entitlement of the Premium and Premium Unlimited plans; partners request an API key by emailing [email protected] from a Tock Dashboard Account Owner. There is no self-serve developer signup; deeper POS, CRM, marketing, loyalty, and ticketing integrations are coordinated through Tock's partnerships team.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Tock the way a machine reads it — 170 machine-readable artifacts across 2 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Tock scores 58.5/100 (developing), with a separate agent-readiness read of 34/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Tock
Each block below is one kind of artifact we hold for Tock. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 2
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Tock Reservation API
Reservation data model and delivery surface published at api.exploretock.com. Reservation records (bookings, ticketed experiences, takeout/delivery orders, parties, pricing, pay...
Tock Guest API
Guest (CRM) data model and ingest surface published at api.exploretock.com. Guest profiles capture contact details, dietary restrictions and preferences, tags, per-business and ...
Open Collections 2
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Tock Guest Model
OPEN COLLECTIONTock Reservation Model
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Tock Plans Pricing
PLANSRate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Tock Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Tock Finops
FINOPSFeatures 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Reservations
Online booking, waitlist, and prepaid/deposit reservations for restaurants and hospitality venues, originally modeled on Alinea Group's prepaid dining workflow.
Ticketed Experiences
Sell tickets for chef's tables, tastings, wine dinners, and one-off events with prepayment, refund rules, and tiered pricing per seating or experience.
Takeout and Delivery
Direct online ordering for pickup and delivery, including wine and retail product sales, with venue-controlled menus and fulfillment windows.
Marketplace Discovery
Diner-facing exploretock.com marketplace that distributes inventory and ticketed experiences across a global network of restaurants and wineries.
Guest CRM
Unified guest profiles capturing reservation history, spend, preferences, allergies, and notes for staff personalization and remarketing.
Operations and Floor Management
Table management, host and server tooling, prep sheets, and shift-level reporting for in-venue operations.
Semantic Vocabularies 2
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Tock Guest Profile Context
JSON-LDTock Reservation Context
JSON-LDSpectral Rules 1
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Tock API Rules
SPECTRALJSON Schema 51
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
tockAddress
JSON SCHEMAtockAuditedNote
JSON SCHEMAtockBusinessGroupGuestProfile
JSON SCHEMAtockBusinessGroupSpend
JSON SCHEMAtockBusinessGuestProfile
JSON SCHEMAtockBusiness
JSON SCHEMAtockBusinessSpend
JSON SCHEMAtockDay
JSON SCHEMAtockDayType
JSON SCHEMAtockExternalIntegrationAttribute
JSON SCHEMAtockGetGuestResponse
JSON SCHEMAtockGuestProfile
JSON SCHEMAtockImportedGuestProfile
JSON SCHEMAtockLink
JSON SCHEMAtockLinkType
JSON SCHEMAtockNoteType
JSON SCHEMAtockOptInSource
JSON SCHEMAtockPatron
JSON SCHEMAtockPhone
JSON SCHEMAtockPhoneType
JSON SCHEMAtockBusiness
JSON SCHEMAtockDiscountDiscountType
JSON SCHEMAtockDiscount
JSON SCHEMAtockExperienceVariety
JSON SCHEMAtockGetReservationResponse
JSON SCHEMAtockGiftCardProviderType
JSON SCHEMAtockGiftCard
JSON SCHEMAtockKeyValue
JSON SCHEMAtockLoyaltyProgramProviderType
JSON SCHEMAtockLoyaltyProgram
JSON SCHEMAtockNoteNoteType
JSON SCHEMAtockNote
JSON SCHEMAtockPartyState
JSON SCHEMAtockPatron
JSON SCHEMAtockPaymentType
JSON SCHEMAtockPayout
JSON SCHEMAtockPurchasedCustomCharge
JSON SCHEMAtockPurchasedExperience
JSON SCHEMAtockPurchasedFee
JSON SCHEMAtockPurchasedOption
JSON SCHEMAtockQuestion
JSON SCHEMAtockRating
JSON SCHEMAtockRatingType
JSON SCHEMAtockRefundRefundStatus
JSON SCHEMAtockRefund
JSON SCHEMAtockReservation
JSON SCHEMAtockSeatingOption
JSON SCHEMAtockTable
JSON SCHEMAtockTockPayment
JSON SCHEMAtockVisitFeedback
JSON SCHEMAtockVisitTag
JSON SCHEMAScroll within the panel for all 51 ·
JSON Structure 51
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Guest Profile Address Structure
JSON STRUCTUREGuest Profile Audited Note Structure
JSON STRUCTUREGuest Profile Business Group Guest Profile Structure
JSON STRUCTUREGuest Profile Business Group Spend Structure
JSON STRUCTUREGuest Profile Business Guest Profile Structure
JSON STRUCTUREGuest Profile Business Spend Structure
JSON STRUCTUREGuest Profile Business Structure
JSON STRUCTUREGuest Profile Day Structure
JSON STRUCTUREGuest Profile Day Type Structure
JSON STRUCTUREGuest Profile External Integration Attribute Structure
JSON STRUCTUREGuest Profile Get Guest Response Structure
JSON STRUCTUREGuest Profile Guest Profile Structure
JSON STRUCTUREGuest Profile Imported Guest Profile Structure
JSON STRUCTUREGuest Profile Link Structure
JSON STRUCTUREGuest Profile Link Type Structure
JSON STRUCTUREGuest Profile Note Type Structure
JSON STRUCTUREGuest Profile Opt In Source Structure
JSON STRUCTUREGuest Profile Patron Structure
JSON STRUCTUREGuest Profile Phone Structure
JSON STRUCTUREGuest Profile Phone Type Structure
JSON STRUCTUREReservation Business Structure
JSON STRUCTUREReservation Discount Discount Type Structure
JSON STRUCTUREReservation Discount Structure
JSON STRUCTUREReservation Experience Variety Structure
JSON STRUCTUREReservation Get Reservation Response Structure
JSON STRUCTUREReservation Gift Card Provider Type Structure
JSON STRUCTUREReservation Gift Card Structure
JSON STRUCTUREReservation Key Value Structure
JSON STRUCTUREReservation Loyalty Program Provider Type Structure
JSON STRUCTUREReservation Loyalty Program Structure
JSON STRUCTUREReservation Note Note Type Structure
JSON STRUCTUREReservation Note Structure
JSON STRUCTUREReservation Party State Structure
JSON STRUCTUREReservation Patron Structure
JSON STRUCTUREReservation Payment Type Structure
JSON STRUCTUREReservation Payout Structure
JSON STRUCTUREReservation Purchased Custom Charge Structure
JSON STRUCTUREReservation Purchased Experience Structure
JSON STRUCTUREReservation Purchased Fee Structure
JSON STRUCTUREReservation Purchased Option Structure
JSON STRUCTUREReservation Question Structure
JSON STRUCTUREReservation Rating Structure
JSON STRUCTUREReservation Rating Type Structure
JSON STRUCTUREReservation Refund Refund Status Structure
JSON STRUCTUREReservation Refund Structure
JSON STRUCTUREReservation Reservation Structure
JSON STRUCTUREReservation Seating Option Structure
JSON STRUCTUREReservation Table Structure
JSON STRUCTUREReservation Tock Payment Structure
JSON STRUCTUREReservation Visit Feedback Structure
JSON STRUCTUREReservation Visit Tag Structure
JSON STRUCTUREScroll within the panel for all 51 ·
Examples 36
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Guest Profile Day Example
EXAMPLEGuest Profile Link Example
EXAMPLEGuest Profile Patron Example
EXAMPLEGuest Profile Phone Example
EXAMPLEReservation Business Example
EXAMPLEReservation Discount Example
EXAMPLEReservation Note Example
EXAMPLEReservation Patron Example
EXAMPLEReservation Payout Example
EXAMPLEReservation Question Example
EXAMPLEReservation Refund Example
EXAMPLEReservation Table Example
EXAMPLEScroll within the panel for all 36 ·
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Fine Dining Reservations
Prepaid and deposit-backed reservations for tasting menus and high-demand seatings, reducing no-shows and stabilizing per-cover revenue.
Wine Country and Tasting Rooms
Ticketed tasting flights, tours, and member experiences for wineries and vineyards with capacity and SKU constraints.
Chef Events and Pop-Ups
Ticketed dinners, collaborations, and limited-run events where prepayment and assigned seating are essential.
Takeout and Wine Delivery
Direct-to-consumer pickup, delivery, and retail wine sales launched and expanded during and after the pandemic.
American Express Dining Benefits
Surfacing curated dining and experience inventory to Amex cardmembers as part of Amex's premium-experience portfolio.
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Point of Sale (POS)
Bi-directional sync with restaurant POS systems for checks, payments, and guest spend; delivered through the contractual Partner API.
CRM and Marketing
Push guest profiles and reservation events into CRM, loyalty, and email/SMS marketing systems via Partner API.
Payments
Integrated card capture and prepayment processing for deposits, tickets, and order payments.
American Express
Owned by American Express since June 2024; integrated with Amex dining benefits, cardmember experiences, and Resy coordination at the parent level.
Squarespace (historical)
Tock was a Squarespace subsidiary from 2021 to mid-2024; some legacy billing and account artifacts may still surface via Squarespace channels for long-tenured customers.
Solutions 4
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Restaurants
Reservations, ticketing, takeout, delivery, and guest CRM for independent and group restaurants.
Wineries
Tastings, tours, club experiences, and on-site retail tooling for wineries and vineyards.
Hotels and Resorts
Dining and experience reservations for on-property restaurants, bars, and signature experiences inside hotels and resorts.
Bars and Lounges
Reservations, ticketed experiences, and walk-in waitlist management for high-demand bar and lounge concepts.
Resources
Every other property we hold for Tock — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 4
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/tock · machine-readable index on apis.io