How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Tripleseat Leads API

Capture and retrieve leads, including the public lead form.

Tripleseat Leads API is one of 7 APIs that Tripleseat publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

This API exposes 24 JSON Schema definitions.

Tagged areas include Leads. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, an API reference, an AsyncAPI specification, a JSON-LD context, and 24 JSON Schemas.

This API exposes 4 operations across 4 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://api.tripleseat.com.

4 operations 4 paths 3 schemas 3 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.tripleseat.com
Authentication
OAuth 2.0
Contact
Terms of Service
Resource Areas
1

Authentication & Security 1

Tripleseat Leads API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the clientCredentials and authorizationCode flows. By default, every request must be authenticated.

  • oauth2 — OAuth 2.0. Access tokens are Bearer tokens that expire after 7200 seconds (2 hours) and are accompanied by a refresh token. OAuth 1.0 is deprecated and discont…

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 3 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Leads 4

Capture and retrieve leads, including the public lead form.

GET
/v1/leads.json
List Leads
listLeads 1 param → 200401429
GET
/v1/leads/{lead_id}.json
Get Lead
getLead 1 param → 200401404
GET
/v1/leads/search.json
Search Leads
searchLeads 2 params → 200401429
POST
/v1/leads/create.json
Create Lead
createLead 2 params body → 201400401

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Lead (16 properties), LeadCreate (12 properties), Error (2 properties). Each schema is shown below with its type and property counts.

LeadCreate
object
Fields accepted when creating a lead via the public lead form.
12 properties 3 required
Lead
object
A potentially interested person or party for outreach.
16 properties
Error
object
A standard error response.
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tripleseat-leads-api-openapi.yml Raw ↑

Other APIs Tripleseat publishes across the network.

Tripleseat Accounts API
Tripleseat Contacts API
Tripleseat Events API
Tripleseat Locations API
Tripleseat Sites API
Tripleseat Users API
Where this information came from

This is an independent, third-party profile of Tripleseat Leads API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.