generated: '2026-10-08'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.fiskil.com/data-api/api-reference/authentication
sources:
- https://docs.fiskil.com/data-api/api-reference/authentication
- https://docs.fiskil.com/data-api/guides/getting-started/authentication
- https://docs.fiskil.com/data-api/api-reference/auth-session
- https://docs.fiskil.com/data-api/guides/core-concepts/auth-sessions
description: Fiskil uses OAuth2 client‑credentials flow to obtain a bearer token which must be sent in the Authorization header.
schemes:
- type: oauth2
  name: Fiskil OAuth2
  evidence: To access the Fiskil API, all requests must be authenticated using a bearer token. This token is obtained by exchanging your API credentials
    ( client_id and client_secret ) via the /v1/token endpoint.
  flows:
  - client_credentials
  token_url: https://api.fiskil.com/v1/token
  how_to_obtain: Generate client_id and client_secret in the Fiskil Developer Console, then POST them to the token endpoint to receive a token.
note: All subsequent API requests must include the token in the Authorization header as "Bearer {access_token}".
docs: https://docs.fiskil.com/data-api/api-reference/authentication