generated: '2026-10-19'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://docs.zespan.com/account/api-keys.md
sources:
- https://docs.zespan.com/account/api-keys.md
- https://docs.zespan.com/api-reference/sdk-cli-support/resolve-project-identity-from-an-api-key.md
- https://docs.zespan.com/cli/auth.md
- https://docs.zespan.com/quickstart.md
description: Authentication methods for Zespan APIs and CLI
schemes:
- type: apiKey
  name: Project API key
  evidence: The SDK sends this key as an `x-api-key` header on requests to the ingest API. If you're calling Zespan's API directly rather than
    through the SDK, set the same header yourself.
  location: header
  header: x-api-key
  how_to_obtain: Create and manage project API keys from the project's Settings → API Keys page in the Zespan dashboard. The key is shown in full
    only once at creation.
- type: http-bearer
  name: Personal API key
  evidence: 'It starts with `lqtp_` and is sent as a Bearer token:'
  location: header
  header: Authorization
  how_to_obtain: Generate and revoke personal API keys from your account settings in the Zespan dashboard.
note: OAuth 2.0 device grant is used by the Zespan CLI for user login, but the documentation does not provide token or authorize URLs, so no OAuth
  flow entry is included.
docs: https://docs.zespan.com/account/api-keys.md