Teambridge · Authentication Profile

Teambridge Authentication

Authentication

Teambridge secures its APIs with apiKey and oauth2 across 2 declared security schemes, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the clientCredentials flow(s).

CompanyWorkforce ManagementSchedulingTime TrackingPayrollHRFrontlineWebhooks
Methods: apiKey, oauth2 Schemes: 2 OAuth flows: clientCredentials API key in: header

Security Schemes

OAuth2 oauth2
· flows: clientCredentials
WebhookSignature apiKey
· in: header (X-Webhook-Signature)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-21'
method: derived
source: openapi/teambridge-openapi-original.json
summary:
  types:
  - apiKey
  - oauth2
  api_key_in:
  - header
  oauth2_flows:
  - clientCredentials
schemes:
- name: OAuth2
  type: oauth2
  flows:
  - flow: clientCredentials
    tokenUrl: https://teambridge.us.auth0.com/oauth/token
    scopes: 1
  sources:
  - openapi/teambridge-openapi-original.json
- name: WebhookSignature
  type: apiKey
  in: header
  parameter: X-Webhook-Signature
  description: |-
    HMAC-SHA256 signature for webhook authentication. The signature is computed from
    the concatenation of the timestamp and request body: `{timestamp}.{body}`.
    The signature header value includes the scheme prefix: `sha256={hex_signature}`.

    Webhook consumers must verify this signature using their webhook secret to ensure
    the request originated from Teambridge.
  sources:
  - openapi/teambridge-openapi-original.json