New: API Reference docs are live — integrate Cleanlist enrichment into your apps. View API docs →
API Reference
Authentication

Authentication

Use a Cleanlist API key for all public API requests.

API Key

API keys are used for programmatic access from your backend, scripts, or integrations.

Getting Your API Key

  1. Log in to portal.cleanlist.ai (opens in a new tab)
  2. Go to Settings -> API Keys
  3. Click Generate Key
  4. Copy and store your key securely
API Keys settings page
API key generation and management

Using Your API Key

Include your key in the Authorization header as a Bearer token:

curl https://api.cleanlist.ai/api/v1/public/auth/validate-key \
  -H "Authorization: Bearer clapi_your_api_key"

Verify Balance Access

curl https://api.cleanlist.ai/api/v1/public/credits/balance \
  -H "Authorization: Bearer clapi_your_api_key"

Response:

{
  "organization_id": "org_123",
  "credits": 1249
}

Key Properties

PropertyDetails
Prefixclapi_
ScopeOrganization-level
HeaderAuthorization: Bearer <api_key>

Public API Rate Limit

LimitScopeWindowOn Exceed
60 requests/minutePer organizationFixed 60-second window429 + Retry-After header

Browser Extension Key

Extension keys (clext_...) are separate from API keys and are used only by the browser extension.

⚠️

Do not use extension keys for public API requests. Public API endpoints require API keys (clapi_...).

Security Best Practices

  1. Never expose API keys in client-side code.
  2. Store keys in environment variables.
  3. Rotate keys periodically.
  4. Monitor usage and revoke compromised keys.
export CLEANLIST_API_KEY="clapi_your_api_key"
 
curl https://api.cleanlist.ai/api/v1/public/credits/balance \
  -H "Authorization: Bearer $CLEANLIST_API_KEY"

What's Next