Tock API
Tock is a reservations, table-management, and event-booking platform for restaurants, bars, and wineries, letting guests book reservations, takeout, and ticketed culinary experiences around the world. This page is an independent design exercise that asks what a well-designed Tock API could look like: the resources it would expose, the authentication it would need, and the workflows it could unlock. Below: a hypothetical endpoint design, the technical requirements a production implementation would face, the use cases programmatic access could serve, and where to start if your team needs this kind of access today.
This page is an independent analysis by Supergood of what a well-designed Tock API could look like. It draws on publicly available information, vendor materials, and general integration experience in this category. Nothing on this page describes an existing Tock product, and Supergood is not affiliated with or endorsed by the vendor. If the vendor offers an official API, we highly recommend it.
What is Tock?
Tock is a reservations, table-management, and event-booking platform for restaurants, bars, and wineries, letting guests book reservations, takeout, and ticketed culinary experiences around the world. Operators use Tock to manage pre-paid bookings and experiences, run events, capture rich guest profiles, and reconcile payments. Acquired by American Express from Squarespace in October 2024, Tock is being combined with Resy into a single reservation platform, bringing its fine-dining and winery inventory under the Resy brand.
Core product areas include:
- Reservations and table management (bookings, walk-ins, party states, seating)
- Experiences and events (ticketed dinners, tastings, add-ons, pre-paid menus)
- Takeout and pickup ordering
- Guest profiles and CRM (visit history, spend, tags, dietary preferences, occasions)
- Payments, refunds, payouts, and discounts on pre-paid bookings
- Data Exports API, Guest Profile Ingest API, and real-time webhooks
An API for a platform like this would naturally organize around its core data entities:
- Reservations (ID, business, date/time, party size, confirmation code, party state)
- Experiences, add-on items, and included menu selections
- Pricing and payments (subtotal, taxes, service charges, gratuity, fees, refunds, payouts)
- Guest profiles (contact, visit and spend history, dietary restrictions, preferences)
- Tags, notes, and special occasions at business and business-group levels
- Operational data (assigned tables, seating areas, servers, feedback, visit metadata)
The Tock Integration Challenge
Restaurants run daily service on Tock, but turning its data into programmatic automation is gated by plan tier, manual key provisioning, and deliberate read-only limits:
- Premium-plan gate: only Premium and Premium Unlimited plans are eligible to receive API or webhook access at all
- Email-request provisioning: API keys and webhooks are issued only after emailing integrate@tockhq.com from an Account Owner on the Dashboard Team page, there is no self-serve developer portal
- Read-only reservations: reservation data cannot be created, modified, or cancelled through the API, those actions stay in the Tock dashboard
- Batch-lagged exports: the Data Exports API generates files only twice daily, each reflecting data as of roughly 12 hours prior, real-time needs depend on webhooks
- Narrow write surface: the Guest Profile Ingest API only allows adding and updating basic guest information and tags, not bookings or payments
- Platform consolidation: with Tock merging into Resy under American Express, integrations must absorb branding, endpoint, and ownership changes during the transition
- Patron-owned fields: dietary restrictions and preferences are patron-controlled and business-read-only, so write-back has to respect ownership boundaries
What a Tock API Could Look Like
If Tock exposed a modern, general-purpose API, the integration challenges above suggest what it would need to get right. This is a design sketch, not documentation of anything that exists today:
- First-class authentication: session handling with support for MFA and enterprise sign-on where the platform uses them
- Consistent resources: normalized JSON schemas and pagination across the platform's core objects
- Reliable writes: idempotency keys and validation that mirrors the platform's own workflow rules
- Entitlement awareness: endpoints scoped to what each customer's licensing actually permits
The endpoint sketches, technical requirements, and use cases below flesh out this hypothetical design.
How AI agents could connect to software like Tock: MCP servers for software without a public API →
Need This Kind of Access Today?
If your team needs this kind of access today, Supergood builds integrations on request, one customer at a time. We act at the direction of our customers, within the access they already hold. Customers bring their own accounts, licenses, and entitlements. If the vendor offers an official API, we highly recommend it.
- Schedule an Integration Assessment
A 30-minute session to review your product mix, licensing, and authentication model. - Scope the Integration
We design the access pattern around your workflows and entitlements. - Deploy with Monitoring
Go live with continuous monitoring as your platforms evolve.
Potential API Endpoints
Authentication
/authenticateWould authenticate to a Tock business using dashboard credentials or an API key and obtain a session for downstream calls.
Reservations
/reservationsWould list reservations and walk-ins with filters for date, party state, experience, and business location.
Reservations
/reservations/{id}Would retrieve a single reservation with pricing, payments, seating, servers, tags, and guest responses.
Experiences
/experiencesWould list bookable experiences, ticketed events, add-on items, and included menu selections.
Guests
/guestsWould retrieve guest profiles with contact details, visit and spend history, preferences, tags, and occasions.
Guests
/guestsWould add or update basic guest information and profile tags via the Guest Profile Ingest surface.
Use Cases
Sync reservation and guest data into your warehouse
- Pull reservations, walk-ins, experiences, and payments across all Tock locations - Stream party-state changes (expected, arrived, seated, no-show, cancelled) in real time - Reconcile guest profiles, visit history, and spend into a unified customer 360
Power CRM and marketing automation
- Push visit, spend, and occasion data into email and loyalty platforms - Ingest enriched guest profiles and tags back into Tock for better service - Trigger win-back and VIP campaigns from real-time guest-profile webhooks
Reconcile payments and event revenue
- Match subtotals, taxes, service charges, gratuity, and fees against your accounting system - Track refunds, payouts, and discounts on pre-paid bookings and ticketed events - Surface deposits and amounts due for finance reporting
Bridge Tock data into operations dashboards
- Feed seating, server, and feedback data into staffing and service-quality tools - Aggregate experience and event demand across venues for forecasting - Monitor real-time reservation flow without manual export downloads
Connect via No-Code Tools
Automate this platform from the no-code stack you already use.
Technical Requirements
Authentication
Would require API key issued via integrate@tockhq.com, plus authenticated dashboard sessions and MFA with managed session handling
Connectivity
Would build on official Data Exports API, Guest Profile Ingest API, and real-time webhooks, supplemented by authenticated dashboard flows
Response format
Normalized JSON across reservations, experiences, payments, and guest-profile objects
Rate limits
Adaptive throttling tuned to your business to stay within Tock-side limits
Session management
Would need automatic session refresh, MFA handling, and API-key rotation
Data freshness
Near real-time via webhooks; twice-daily Data Exports otherwise reflect data as of ~12 hours prior
Security
Encrypted credential vault, scoped tokens, SOC 2-aligned controls, and audit logging
Webhooks
Real-time callbacks for reservation, walk-in, and guest-profile updates
Latency
Design target: sub-second reads on cached reservation and guest entities; multi-second writes on guest ingest
Throughput
Design target: horizontally scaled workers sized to multi-location reservation and guest volume
Reliability
Retry, backoff, and idempotency keys for guest ingest and webhook reconciliation
Versioning
Clear versioning and change management would matter as Tock evolves
Frequently asked questions
Availability of official interfaces varies by product, plan, and licensing. Many platforms in this category gate access behind partner programs or paid modules, and there is often no broadly available, self-serve public API. Check the vendor's developer resources for current offerings.
The hard parts would be authentication (MFA, session management, enterprise controls), consistent schemas across the platform's products, and write semantics that reconcile the way the platform's own workflows do.
No. This page is an independent analysis by Supergood and is not affiliated with, sponsored by, or endorsed by the vendor. All product names and trademarks belong to their respective owners and are used for identification only. Nothing here documents an actual Tock product or service.
Supergood acts at the direction of its customers, within the access those customers already have. We respect each customer's agreements with their software vendors, and how those agreements apply to a customer's use is a determination the customer makes. If the vendor offers an official API, we highly recommend it.
Supergood builds managed API access to enterprise software for customers on request, scoped to each customer's own licensing and entitlements. If your team needs programmatic access to a platform like this, schedule an integration assessment to discuss options.