Clearbit API keys
Clearbit API credentials belong in configuration, not in a commit. This page covers where to create one, what it looks like, and how APIKeyConnect stores it without ever being able to read it.
The facts
- Category
- Data & Analytics
- API host
api.clearbit.com- Key format
sk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx- Env variable
CLEARBIT- Sensitivity
- Medium
- Create a key
- https://dashboard.clearbit.com/api — Sign in, then Settings → Keys & Settings. API keys exist only on legacy Clearbit accounts — new enrichment is sold as HubSpot Breeze.
- Documentation
- https://dashboard.clearbit.com/docs
A leaked key here is mostly a billing and quota problem rather than a data one — still worth rotating, rarely an emergency.
Kinds of Clearbit key
API Key
How APIKeyConnect stores it
The key is encrypted in your browser with AES-256-GCM, under a key derived from your master password with PBKDF2-SHA-256 at 600,000 iterations. The password never leaves your device, and the server holds ciphertext it has no way to open.
What the server can see — and what this design does not protect against — is written out in full on the security page. That section exists because a page with no limits section is marketing.
Questions
Where do I get a Clearbit API key?
Clearbit issues keys from https://dashboard.clearbit.com/api. Sign in, then Settings → Keys & Settings. API keys exist only on legacy Clearbit accounts — new enrichment is sold as HubSpot Breeze. Once you have it, store it in APIKeyConnect rather than in a .env file you might commit — the key is encrypted on your device with a master password we never receive.
What does a Clearbit API key look like?
Clearbit keys follow the pattern sk_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx. Knowing the shape is useful for spotting one that has been pasted into a commit, a log line, or a support ticket — the places keys leak from most often.
What environment variable should I use for Clearbit?
Most projects use CLEARBIT. APIKeyConnect recognises these names, so importing an existing .env maps the value onto Clearbit automatically instead of leaving it as an unlabelled string, and generating a .env writes it back under the same name.
How dangerous is a leaked Clearbit key?
Medium sensitivity. A leaked key here is mostly a billing and quota problem rather than a data one — still worth rotating, rarely an emergency.
Can APIKeyConnect see my Clearbit key?
No. The key is encrypted in your browser with AES-256-GCM under a key derived from your master password (PBKDF2-SHA-256, 600,000 iterations). The password never leaves your device and the server stores ciphertext it cannot open. What the server can see is documented in full on the security page, including what this design does not protect against.