Skip to documentation content

Authenticate enrichment workloads

Use environment-scoped server credentials and least-privilege enrichment scopes.

In this guide
  1. 1Keep keys server-side
  2. 2Separate Sandbox and Production
  3. 3Grant explicit scopes
In this guide
  1. 1Keep keys server-side
  2. 2Separate Sandbox and Production
  3. 3Grant explicit scopes

Bearer authentication

Send the workspace key in the Authorization header from server-side code only. Data Enrichment keys use the enrich_live_ or enrich_test_ prefix.

HTTP
Authorization: Bearer enrich_live_••••••••

Scope by workload

ScopePurpose
entities:resolveResolve organizations and people
enrich:writeSubmit enrichment jobs
jobs:readRead job state and results
evidence:readRead provenance and candidate evidence
graph:readValidate and execute graph queries
webhooks:writeManage signed result destinations

Rotate without downtime

Create a replacement in the same environment, deploy it, verify successful jobs, and revoke the old key only after traffic has moved.

Was this page helpful?