Tock
Tock is a restaurant and hospitality reservations, events, and ordering platform used by restaurants, wineries, bars, and hotels to manage bookings, prepaid experiences, waitlists, and guest data. Tock is owned by American Express (acquired from Squarespace in 2024). Tock exposes a partner and enterprise-gated data API and webhook program rather than an open self-serve developer API - access is limited to Premium and Premium Unlimited plans and is provisioned by request to Tock. The documented surface consists of a twice-daily Data Exports API for historical reservation and guest data, a Guest Profile Ingest API for adding and updating basic guest information and tags, and real-time reservation and guest-profile webhooks. Reservation records cannot be created or manipulated through the API. Data-model reference documentation is published publicly at api.exploretock.com, but concrete endpoint paths, methods, and OpenAPI definitions are only shared with approved partners; the API entries below are modeled from the public data model and API FAQ.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Tock the way a machine reads it — 6 machine-readable artifacts across 4 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 18.1/100 (emerging), with a separate agent-readiness read of 0/100 (human only). 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.
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 4
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 Data Exports API
Twice-daily export of all historical reservation and guest data for the locations in a Tock business group. Payloads follow the published Reservation data model (party, purchase...
Tock Guest Profile Ingest API
Add and update basic guest information and guest-profile tags in Tock, following the published Guest data model (patron identity, contact details, dietary restrictions, hospital...
Tock Real-time Reservation Webhook
Real-time webhook that delivers reservation updates for all locations within a Tock business group to a partner-supplied endpoint URL. The partner provides the receiving endpoin...
Tock Real-time Guest Profile Webhook
Real-time webhook that delivers guest-profile updates for all locations within a Tock business group to a partner-supplied endpoint URL. Tock POSTs guest-profile events shaped b...
Pricing 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.
Security Posture 1
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.
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.
Documentation 2
Reference material describing how the API behaves
Access & Security 1
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/tock-reservations · machine-readable index on apis.io