Tripleseat website screenshot

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.

1 APIs 5 Features
RestaurantEventsCateringLeadsWebhooksSales

APIs

Tripleseat API

The Tripleseat REST API provides access to leads, events, accounts, contacts, locations, sites, and users for event and catering sales workflows. A public lead form endpoint cap...

Collections

Pricing Plans

Tripleseat Plans Pricing

5 plans

PLANS

Rate Limits

Tripleseat Rate Limits

4 limits

RATE LIMITS

FinOps

Features

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.

Use Cases

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

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.

Event Specifications

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...

ASYNCAPI

Semantic Vocabularies

Tripleseat Api Context

10 classes · 25 properties

JSON-LD

Tripleseat Webhooks Context

2 classes · 8 properties

JSON-LD

API Governance Rules

Tripleseat API Rules

33 rules · 7 errors 20 warnings 6 info

SPECTRAL

JSON Structure

Tripleseat Api Account Structure

10 properties

JSON STRUCTURE

Tripleseat Api Account Update Structure

7 properties

JSON STRUCTURE

Tripleseat Api Contact Create Structure

5 properties

JSON STRUCTURE

Tripleseat Api Contact Structure

8 properties

JSON STRUCTURE

Tripleseat Api Event Structure

11 properties

JSON STRUCTURE

Tripleseat Api Lead Create Structure

12 properties

JSON STRUCTURE

Tripleseat Api Lead Structure

16 properties

JSON STRUCTURE

Tripleseat Api Location Structure

7 properties

JSON STRUCTURE

Tripleseat Api Site Structure

2 properties

JSON STRUCTURE

Tripleseat Api User Structure

5 properties

JSON STRUCTURE

Tripleseat Webhooks Webhook Headers Structure

1 properties

JSON STRUCTURE

Tripleseat Webhooks Webhook Payload Structure

3 properties

JSON STRUCTURE

Example Payloads

Tripleseat Api Account Example

10 fields

EXAMPLE

Tripleseat Api Event Example

11 fields

EXAMPLE

Tripleseat Api Lead Example

16 fields

EXAMPLE

Tripleseat Api Site Example

2 fields

EXAMPLE

Tripleseat Api User Example

5 fields

EXAMPLE

Resources

🔗
Website
Website
🔗
Documentation
Documentation
💬
Support
Support
👥
GitHubOrganization
GitHubOrganization
📰
Blog
Blog
🔗
Marketplace
Marketplace
🔗
Partners
Partners
💰
Pricing
Pricing
🔗
LinkedIn
LinkedIn
🔗
SpectralRules
SpectralRules
🔗
Vocabulary
Vocabulary
🔗
Plans
Plans
🔗
RateLimits
RateLimits
🔗
FinOps
FinOps

Sources

Raw ↑
opencollection: 1.0.0
info:
  name: Tripleseat API
  version: v1
request:
  auth:
    type: oauth2
    flow: client_credentials
    accessTokenUrl: https://api.tripleseat.com/oauth/token
    credentials:
      clientId: '{{clientId}}'
      clientSecret: '{{clientSecret}}'
items:
- info:
    name: Leads
    type: folder
  items:
  - info:
      name: List Leads
      type: http
    http:
      method: GET
      url: https://api.tripleseat.com/v1/leads.json
      params:
      - name: page
        value: ''
        type: query
        description: The page of results to return. Each page contains 50 records.
    docs: Retrieve a paginated list of leads. Returns 50 records per page; use the page query parameter to page through results.
  - info:
      name: Get Lead
      type: http
    http:
      method: GET
      url: https://api.tripleseat.com/v1/leads/:lead_id.json
      params:
      - name: lead_id
        value: ''
        type: path
        description: The unique identifier of the lead.
    docs: Retrieve information for a single lead by its identifier.
  - info:
      name: Search Leads
      type: http
    http:
      method: GET
      url: https://api.tripleseat.com/v1/leads/search.json
      params:
      - name: page
        value: ''
        type: query
        description: The page of results to return. Each page contains 50 records.
      - name: updated_after
        value: '2026-06-03T14:30:00Z'
        type: query
        description: Return leads updated after this timestamp.
    docs: Retrieve leads matching the supplied query parameters.
  - info:
      name: Create Lead
      type: http
    http:
      method: POST
      url: https://api.tripleseat.com/v1/leads/create.json
      params:
      - name: public_key
        value: example
        type: query
        description: The public key for the lead form site or location.
      - name: location_id
        value: '500123'
        type: query
        description: The location the lead is intended for. Required when the site has more than one location and not supplied
          in the body.
      body:
        type: json
        data: '{}'
    docs: Create a lead from a public lead form using a public key. The request body wraps lead fields in a lead object. If
      the site has more than one location, location_id must be supplied in the body or as a query parameter.
- info:
    name: Events
    type: folder
  items:
  - info:
      name: List Events
      type: http
    http:
      method: GET
      url: https://api.tripleseat.com/v1/events.json
      params:
      - name: page
        value: ''
        type: query
        description: The page of results to return. Each page contains 50 records.
      - name: order
        value: example
        type: query
        description: Field to order results by (for example, event_start).
      - name: sort_direction
        value: asc
        type: query
        description: Sort direction for the ordered field.
    docs: Retrieve a paginated list of events. Returns 50 records per page; use the page query parameter to page through results.
  - info:
      name: Get Event
      type: http
    http:
      method: GET
      url: https://api.tripleseat.com/v1/events/:event_id.json
      params:
      - name: event_id
        value: ''
        type: path
        description: The unique identifier of the event.
    docs: Retrieve information for a single event by its identifier.
  - info:
      name: Search Events
      type: http
    http:
      method: GET
      url: https://api.tripleseat.com/v1/events/search.json
      params:
      - name: page
        value: ''
        type: query
        description: The page of results to return. Each page contains 50 records.
      - name: updated_after
        value: '2026-06-03T14:30:00Z'
        type: query
        description: Return events updated after this timestamp.
    docs: Retrieve events matching the supplied query parameters.
- info:
    name: Accounts
    type: folder
  items:
  - info:
      name: List Accounts
      type: http
    http:
      method: GET
      url: https://api.tripleseat.com/v1/accounts.json
      params:
      - name: page
        value: ''
        type: query
        description: The page of results to return. Each page contains 50 records.
    docs: Retrieve a paginated list of accounts.
  - info:
      name: Get Account
      type: http
    http:
      method: GET
      url: https://api.tripleseat.com/v1/accounts/:account_id.json
      params:
      - name: account_id
        value: ''
        type: path
        description: The unique identifier of the account.
    docs: Retrieve information for a single account by its identifier.
  - info:
      name: Update Account
      type: http
    http:
      method: PUT
      url: https://api.tripleseat.com/v1/accounts/:account_id.json
      params:
      - name: account_id
        value: ''
        type: path
        description: The unique identifier of the account.
      body:
        type: json
        data: '{}'
    docs: Update an existing account by its identifier.
- info:
    name: Contacts
    type: folder
  items:
  - info:
      name: Create Contact
      type: http
    http:
      method: POST
      url: https://api.tripleseat.com/v1/contacts.json
      body:
        type: json
        data: '{}'
    docs: Create a contact and associate it with an account. Every contact must be associated with an account via account_id.
- info:
    name: Locations
    type: folder
  items:
  - info:
      name: List Locations
      type: http
    http:
      method: GET
      url: https://api.tripleseat.com/v1/locations.json
    docs: Retrieve all locations housed within a site.
- info:
    name: Sites
    type: folder
  items:
  - info:
      name: List Sites
      type: http
    http:
      method: GET
      url: https://api.tripleseat.com/v1/sites.json
    docs: Retrieve sites. A site represents a group of venues or locations. Creating, updating, or deleting sites via the
      API is not supported.
- info:
    name: Users
    type: folder
  items:
  - info:
      name: List Users
      type: http
    http:
      method: GET
      url: https://api.tripleseat.com/v1/users.json
      params:
      - name: page
        value: ''
        type: query
        description: The page of results to return. Each page contains 50 records.
    docs: Retrieve users who can log into your Tripleseat. Creating, updating, or deleting users via the API is not supported.
  - info:
      name: Get User
      type: http
    http:
      method: GET
      url: https://api.tripleseat.com/v1/users/:user_id.json
      params:
      - name: user_id
        value: ''
        type: path
        description: The unique identifier of the user.
    docs: Retrieve information for a single user by identifier.
bundled: true