Integration guides

API key management

Updated

Create, configure, and secure API keys with permissions, rate limits, and expiration.

Your keys work out of the box with full access and no configuration needed. This guide covers optional features you can use as your integration grows.

1. Create a key

Open API Keys in the dashboard.
Click Create API Key and give it a name (e.g. prod-backend, staging-sync).
Copy and store it securely.

That's it: your key is ready to use with full access to all endpoints.

2. Fine-tune permissions (optional)

By default, every key has full access. No setup needed. As your team grows, you can scope each key to specific capabilities:

Scope	What it covers
Person Enrichment	Enrich person profiles from Social URLs, emails or names
Company Enrichment	Enrich company profiles from Social URLs or domains
Search	Search people and companies, including lookalikes and Agentic Search
Contact (Email & Phone)	Find professional email addresses and phone numbers

Select only the scopes your integration needs, or leave them all checked for full access.

If a key tries to call an endpoint outside its scopes, the API returns a 403 status code.

3. Set rate limits (optional)

Per-key rate limits let you protect your workspace budget by capping individual integrations:

Setting	Description
RPM limit	Maximum requests per minute for this key
Daily limit	Maximum requests per day for this key

If you don't set any, your workspace defaults apply automatically. Per-key limits can only cap usage below the workspace maximum. They can never exceed it.

When a per-key limit is reached, the API returns 429 Too Many Requests.

4. Add an expiration date (optional)

Useful for temporary access: contractor keys, demo integrations, or test environments. After the date you choose, the key stops working automatically.

You can change or remove the expiration anytime by editing the key.

Manage existing keys

Edit. Click the edit icon on any active key to update its name, permissions, rate limits, or expiration. Changes take effect immediately.

Revoke. Revoked keys stop working immediately. They stay visible in the table for reference, but cannot be reactivated. When in doubt, create a new key first, update your integration, then revoke the old one.

Quick tips

One key per environment. Separate keys for dev, staging, and production keep things clean.
Name keys clearly. A name like prod-crm-sync or staging-enrichment makes auditing easy.
Scope when you need to. Start with full access. Restrict later as your team and integrations grow.

Something not working?

Symptom	Fix
`403 Forbidden`	The key is missing a required permission. Edit it in API Keys
`429 Too Many Requests`	A per-key rate limit was reached. Raise it or wait for the reset
`401 Unauthorized` (expired key)	The key passed its expiration date. Create a new one

For all error codes and retry strategies, see Error handling & retries.