Enrich · Authentication Profile

Enrich So Authentication

Authentication

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

Data EnrichmentContact DiscoveryWeb IntelligenceB2B DataLead EnrichmentEmail FinderEmail VerificationPhone NumbersLinkedInReference Data
Methods: apiKey, http Schemes: 2 OAuth flows: API key in:

Security Schemes

apiKeyHeader apiKey
· in: header ()
bearerAuth http
scheme: bearer

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-11'
method: derived
source: openapi/enrich-so-openapi.yml
summary:
  types:
  - apiKey
  - http
schemes:
- name: apiKeyHeader
  type: apiKey
  in: header
  keyName: x-api-key
  description: >-
    API key passed in the x-api-key header (recommended). Keys are created and managed in
    the Enrich dashboard at https://dash.enrich.so/dashboard/api-keys and are prefixed with
    sk_ (for example sk_prod_...). A missing, invalid, or disabled key returns 401.
  sources:
  - https://doc.enrich.so/authentication-1951026m0
  - openapi/enrich-so-openapi.yml
- name: bearerAuth
  type: http
  scheme: bearer
  description: >-
    The same API key may alternatively be sent as an Authorization Bearer token
    (Authorization: Bearer [example key]).
  sources:
  - https://doc.enrich.so/authentication-1951026m0
  - openapi/enrich-so-openapi.yml