Tabs · Authentication Profile

Tabs Authentication

Authentication

Tabs 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 authorizationCode and deviceCode flow(s).

BillingRevenue AutomationAccounts ReceivableRevenue RecognitionUsage-Based BillingInvoicingCollectionsFintechSaaS
Methods: apiKey, oauth2 Schemes: 2 OAuth flows: authorizationCode, deviceCode API key in: header

Security Schemes

custom-header apiKey
· in: header (Authorization)
mcp-oauth oauth2
· flows: authorizationCode, deviceCode

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-21'
method: searched
source: openapi/tabs-external-api-openapi.yml, openapi/tabs-usage-api-beta-openapi.yml
docs: https://docs.tabsplatform.com/docs/authentication
summary:
  types:
  - apiKey
  - oauth2
  api_key_in:
  - header
  oauth2_flows:
  - authorizationCode
  - deviceCode
schemes:
- name: custom-header
  type: apiKey
  in: header
  parameter: Authorization
  format: "Authorization: <API_KEY> (Usage API docs also show 'Authorization: Bearer <your-key>')"
  issuance: >-
    Admins generate API keys in the Developers section of the Tabs app side
    navigation; non-admins must request one from their Tabs administrator.
    Keys identify the merchant and the scopes they may access; revocation
    takes effect after eviction from an hourly cache. Self-service key
    rotation is on the roadmap per the docs.
  sources:
  - openapi/tabs-external-api-openapi.yml
  - openapi/tabs-usage-api-beta-openapi.yml
- name: mcp-oauth
  type: oauth2
  description: >-
    OAuth 2.0 (WorkOS-backed) protects the Tabs MCP server at
    https://integrators.prod.api.tabsplatform.com/mcp — not the REST API,
    which is API-key only. Standard discovery via RFC 8414 + RFC 9728
    metadata; PKCE S256; dynamic client registration; automatic merchant
    scoping.
  flows:
  - flow: authorizationCode
    authorizationUrl: https://login.tabs.com/oauth2/authorize
    tokenUrl: https://login.tabs.com/oauth2/token
  - flow: deviceCode
    authorizationUrl: https://login.tabs.com/oauth2/device_authorization
    tokenUrl: https://login.tabs.com/oauth2/token
  scopes_supported: [openid, profile, email, offline_access]
  sources:
  - well-known/tabs-oauth-authorization-server.json
  - well-known/tabs-mcp-oauth-protected-resource.json
  - well-known/tabs-openid-configuration.json