Crunchbase · Authentication Profile

Crunchbase Data Authentication

Authentication

Crunchbase secures its APIs with apiKey across 2 declared security schemes, as derived from its OpenAPI definitions.

Company DataWeb IntelligenceFunding DataFirmographicsB2B DataInvestor DataReference DataFortune 1000
Methods: apiKey Schemes: 2 OAuth flows: API key in:

Security Schemes

userKeyQuery apiKey
· in: query (user_key)
userKeyHeader apiKey
· in: header (X-cb-user-key)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/crunchbase-data-openapi.yml
summary:
  types:
  - apiKey
schemes:
- name: userKeyQuery
  type: apiKey
  in: query
  parameter: user_key
  description: >-
    API key passed as the user_key query parameter, e.g.
    ?user_key=YOUR_API_KEY. Issued with a Crunchbase Enterprise, Applications,
    or Basic license.
  sources:
  - openapi/crunchbase-data-openapi.yml
  - https://data.crunchbase.com/docs/using-the-api
- name: userKeyHeader
  type: apiKey
  in: header
  parameter: X-cb-user-key
  description: >-
    API key passed as the X-cb-user-key request header. Preferred over the
    query parameter to avoid leaking the key in logs and URLs.
  sources:
  - openapi/crunchbase-data-openapi.yml
  - https://data.crunchbase.com/docs/using-the-api
notes: >-
  All requests must use HTTPS; non-HTTPS calls return HTTP 426. API keys are
  license-gated - full API access requires a Crunchbase Enterprise or
  Applications license, with a reduced Basic API for Crunchbase Basic plan
  holders. There is no OAuth or user-delegated flow; access is a single
  account-level API key.