Puzzle · Authentication Profile

Puzzle Authentication

Authentication

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

CompanyAccountingFinancialBookkeepingFintechGeneral LedgerPayrollAgent-NativeMCP
Methods: oauth2 Schemes: 1 OAuth flows: authorizationCode API key in:

Security Schemes

OAuth2 oauth2
scheme: oauth2

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-20'
method: searched
source: https://puzzle-api.readme.io/docs/getting-started
docs: https://puzzle-api.readme.io/docs/getting-started
summary:
  types: [oauth2]
  oauth2_flows: [authorizationCode]
  pkce: true
  legacy: link-token (deprecated)
schemes:
- name: OAuth2
  type: oauth2
  scheme: oauth2
  flow: authorizationCode
  pkce: true
  authorizationUrl: https://api.puzzle.io/oauth/authorize
  tokenUrl: https://api.puzzle.io/oauth/token
  sandbox_authorizationUrl: https://staging.southparkdata.com/oauth/authorize
  sandbox_tokenUrl: https://staging.southparkdata.com/oauth/token
  token_endpoint_auth: >-
    Clients may authenticate at the token endpoint via HTTP Basic (recommended for
    confidential clients) or by including client_id / client_secret in the
    x-www-form-urlencoded body.
  credentials:
  - client_id
  - client_secret
  - connection_key
  refresh: refresh_token grant supported; offline_access scope for long-lived access
notes: >-
  Authentication is OAuth 2.0 Authorization Code flow with PKCE. Partners request a
  client ID, client secret, and connection key from Puzzle (api@puzzle.io) and register
  valid redirect URIs. A legacy link-token flow exists for existing partners but is
  deprecated in favor of OAuth. The current user can be identified via the /me endpoint,
  valid only for OAuth connections. The OpenAPI document does not declare securitySchemes;
  this profile is captured from the developer documentation.