Tripleseat · Authentication Profile

Tripleseat Authentication

Authentication

Tripleseat secures its APIs with oauth2 across 1 declared security scheme, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode and clientCredentials flow(s).

RestaurantEventsCateringLeadsWebhooksSales
Methods: oauth2 Schemes: 1 OAuth flows: authorizationCode, clientCredentials API key in:

Security Schemes

oauth2 oauth2
· flows: clientCredentials, authorizationCode

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/tripleseat-openapi.yml
summary:
  types:
  - oauth2
  oauth2_flows:
  - authorizationCode
  - clientCredentials
schemes:
- name: oauth2
  type: oauth2
  flows:
  - flow: clientCredentials
    tokenUrl: https://api.tripleseat.com/oauth/token
    scopes: 0
  - flow: authorizationCode
    authorizationUrl: https://api.tripleseat.com/oauth/authorize
    tokenUrl: https://api.tripleseat.com/oauth/token
    scopes: 0
  description: 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 discontinued
    on July 1, 2026.
  sources:
  - openapi/tripleseat-openapi.yml