Skip to main content
The External API uses a dedicated API key in the x-api-key header. It does not accept lev8 user-session tokens or internal service keys.

​
Create and store a key

Create a key from API Tokens in your lev8 workspace. The complete value is shown once. After that, lev8 only displays a masked form such as lev8_live_ab12cd34ef56_****.
Treat the complete key as a secret. Store it in a secrets manager or encrypted environment configuration. Never embed it in frontend JavaScript, mobile applications, public repositories, analytics events, or log messages.

​
Key lifecycle

  • Keys belong to the user who created them.
  • Revocation takes effect immediately. Repeated revocation is safe.
  • Existing keys cannot be recovered from the dashboard; create a replacement and rotate clients instead.
  • API scopes and expiration are currently managed by lev8 and cannot be customized during key creation.
  • Any active key can query its own billing account’s credit balance; Entity Search and Contact Search each depend on the key’s endpoint scope.
  • Multiple keys for the same user share the same user-level concurrency allowance.

​
Authentication errors

These responses use the standard error envelope and do not expose credential records or dependency details.