Tripleseat API
Tripleseat's REST API is self-serve: venues enable it in settings and generate credentials. OAuth 2.0 is current, with OAuth 1.0 discontinued July 1, 2026, and HMAC-signed webhooks are first class. There is no sandbox and no SDK, and docs live in a Zendesk help center.
Frequently asked questions
Tripleseat scores C on Supergood's API Report Card. Tripleseat's REST API is self-serve: venues enable it in settings and generate credentials. OAuth 2.0 is current, with OAuth 1.0 discontinued July 1, 2026, and HMAC-signed webhooks are first class. There is no sandbox and no SDK, and docs live in a Zendesk help center.
Tripleseat has an official API, but teams routinely hit its limits: gated access, partial coverage, or paid tiers. Most end up supplementing it with exports or an unofficial API layer like Supergood. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Tripleseat is a sales-and-event-management SaaS platform built specifically for restaurants, hotels, and unique venues.
POS / Hospitality - specifically event sales, catering and group bookings inside restaurants, hotels, breweries, wineries, eatertainment venues, and wedding/unique venues. Venues use Tripleseat to: capture inbound event leads from website forms, EventUp marketplace, The Knot, WeddingWire and partner channels; route leads to sales reps and track them through a CRM pipeline (accounts, contacts, tasks, calendar); generate proposals, contracts, BEOs and invoices from templates; build floor plans (2D and 3D) and assign rooms/tables to bookings; collect deposits, ticket revenue and final payments via Stripe/Square/Fiserv; sync events to POS (OpenTable, Tock, SevenRooms, Toast), hotel PMS (Mews, Oracle OPERA, WebRezPro, Stayntouch), and calendar (Google, Outlook); push leads/contacts into email marketing (Mailchimp, Constant Contact); manage staffing handoffs to BOH and event staff apps; and report on conversion rates, sales rep performance, room utilization, F&B revenue and lead source attribution.
High within its niche. Tripleseat is the de facto category leader for restaurant private-dining and group-event CRM in North America.
Event and booking records (date, time, room/space, headcount, F&B menu, pricing), leads with full contact PII (name, email, phone, event type, budget, source attribution), accounts (corporate clients, wedding couples, repeat hosts), BEOs and contracts (signed PDFs, payment terms), payment transactions and stored cards (PCI-scoped via Stripe/Square/Fiserv), floor plans and room/table inventory, sales rep activity and pipeline, ticketed-event sales (TripleseatDirect), room blocks (hotels), POS-synced check and menu-item spend, marketing opt-ins and email engagement, and analytics around conversion, sales rep performance and revenue per room.
Founded 2008, ~18 years old.
Supergood's grades measure one thing: can a customer's engineering team get their own data out programmatically? Supergood checks six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and rolls them into a letter grade. Supergood re-verifies grades, and they only move on evidence.
Yes, via a managed API layer. Supergood builds REST APIs and MCP servers for authenticated enterprise web apps, so AI agents and internal tools can read and write data programmatically. Site terms may apply to any integration approach, and how they apply is a determination each team makes for itself.
Not that we could find. As of August 2026 there is no official Tripleseat MCP server in any public registry, and no maintained community server we're aware of. We re-verify this periodically — report an inaccuracy below if we missed one.
Not natively. Tripleseat doesn't publish an MCP server, so MCP clients like Claude, Cursor, and Codex have nothing to connect to out of the box. If that changes, this page will reflect it.