Crisphive Com Authentication

generated: '2026-11-04'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.crisphive.com/docs/login-and-api-keys
sources:
- https://docs.crisphive.com/docs/login-and-api-keys
- https://docs.crisphive.com/docs/authentication
- https://docs.crisphive.com/docs/oauth
- https://docs.crisphive.com/technical-reference/authentication
description: Authentication methods for Crisphive APIs
schemes:
- type: http-bearer
  name: API Key
  evidence: Authentication Requests are authenticated with a secret API key sent as a bearer token on every call. The Authorization header Include
    your API key as a bearer token.
  location: header
  header: Authorization
  how_to_obtain: Create keys from the dashboard under Settings → Developers; the key value is shown once at creation.
- type: oauth2
  name: OAuth 2.1
  evidence: Let your users connect their own Crisphive business to your product — OAuth 2.1 with a consent screen, no API key ever copied.
  flows:
  - authorization_code
  - refresh_token
  authorize_url: /oauth/authorize
  scopes:
  - customers_view
  - job_view
  how_to_obtain: Register a client dynamically via POST /oauth/register to receive a client_id (and secret for verified partners). Then follow
    the authorization code flow.
note: All URLs are taken directly from the documentation and are relative to the Crisphive API host.
docs: https://docs.crisphive.com/docs/login-and-api-keys