Tripleseat
Tripleseat is event management and catering sales software for restaurants, hotels, and unique venues, helping operators capture leads, book events, and manage the sales lifecycle. Tripleseat provides a public REST API and webhooks for partners and customers to integrate event and lead data with external systems. The API exposes endpoints for leads, events, accounts, contacts, locations, sites, and users, and supports a public lead form for capturing inquiries directly into Tripleseat. Webhooks emit trigger events such as CREATE_LEAD, CONVERT_LEAD, and CONVERT_LEAD_TO_BOOKING, signed with a SHA256-HMAC X-Signature header. Authentication moved from OAuth 1.0 to OAuth 2.0, with OAuth 1.0 discontinued on July 1, 2026, and v1 endpoints served from api.tripleseat.com.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Tripleseat the way a machine reads it — 71 machine-readable artifacts across 7 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 — Tripleseat scores 62.7/100 (strong), with a separate agent-readiness read of 54/100 (agent ready). 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 Tripleseat
Each block below is one kind of artifact we hold for Tripleseat. 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 7
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.
Tripleseat Accounts API
Retrieve and update accounts.
Tripleseat Contacts API
Create and associate contacts with accounts.
Tripleseat Events API
Retrieve events and their bookings.
Tripleseat Leads API
Capture and retrieve leads, including the public lead form.
Tripleseat Locations API
Retrieve locations within a site.
Tripleseat Sites API
Retrieve sites that group locations.
Tripleseat Users API
Retrieve Tripleseat users.
Scroll within the panel for all 7 ·
Open Collections 1
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).
Tripleseat API
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.
Rate 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.
Tripleseat 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.
Tripleseat Finops
FINOPSFeatures 5
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.
Lead Capture
Capture inquiries through the public lead form API and the leads endpoints, routing leads to the correct location.
Event And Booking Management
Retrieve and manage events and bookings across the sales lifecycle.
Account And Contact CRM
Maintain accounts and their associated contacts for customer records.
Webhooks
Subscribe to lead and booking lifecycle events, verified with a SHA256-HMAC X-Signature header.
Multi-Location Support
Model sites that group multiple locations and target leads and events at specific locations.
Event Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Tripleseat Webhooks
Tripleseat webhooks POST a JSON package to a subscriber URL when a lead or booking lifecycle event occurs. Each request carries an X-Signature header computed with SHA256-HMAC u...
ASYNCAPISemantic 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.
Tripleseat Api Context
JSON-LDTripleseat Webhooks Context
JSON-LDSpectral Rules 3
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.
JSON Schema 12
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.
Account
JSON SCHEMAAccountUpdate
JSON SCHEMAContactCreate
JSON SCHEMAContact
JSON SCHEMAEvent
JSON SCHEMALeadCreate
JSON SCHEMALead
JSON SCHEMALocation
JSON SCHEMASite
JSON SCHEMAUser
JSON SCHEMAWebhookHeaders
JSON SCHEMAWebhookPayload
JSON SCHEMAScroll within the panel for all 12 ·
JSON Structure 12
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.
Tripleseat Api Account Structure
JSON STRUCTURETripleseat Api Account Update Structure
JSON STRUCTURETripleseat Api Contact Create Structure
JSON STRUCTURETripleseat Api Contact Structure
JSON STRUCTURETripleseat Api Event Structure
JSON STRUCTURETripleseat Api Lead Create Structure
JSON STRUCTURETripleseat Api Lead Structure
JSON STRUCTURETripleseat Api Location Structure
JSON STRUCTURETripleseat Api Site Structure
JSON STRUCTURETripleseat Api User Structure
JSON STRUCTURETripleseat Webhooks Webhook Headers Structure
JSON STRUCTURETripleseat Webhooks Webhook Payload Structure
JSON STRUCTUREScroll within the panel for all 12 ·
Examples 12
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.
Tripleseat Api Event Example
EXAMPLETripleseat Api Lead Example
EXAMPLETripleseat Api Site Example
EXAMPLETripleseat Api User Example
EXAMPLEScroll within the panel for all 12 ·
Security Posture 3
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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 4
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.
Website Lead Forms
Embed a public lead form on a website to push inquiries directly into Tripleseat via the lead form API.
CRM And Marketing Sync
Synchronize accounts, contacts, and events with external CRM and email marketing platforms.
Real-Time Integrations
React to lead creation and conversion in real time using webhooks to drive downstream automation.
Reporting And Analytics
Extract events and leads into data warehouses and dashboards for sales reporting.
Integrations 4
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
SevenRooms
Reservation, seating, and guest management platform that shares reservation and event details with Tripleseat.
OpenTable Guest Center
Connect Tripleseat events to OpenTable guest center bookings to avoid double bookings.
Tock
Collect private event leads from Tock and transfer them into Tripleseat.
Square
Tripleseat integration available through the Square App Marketplace.
Resources
Every other property we hold for Tripleseat — 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 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 4
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/tripleseat · machine-readable index on apis.io