Docs
Docs
No login needed to read any of this. Every page carries the date it was last changed, and the API changelog lists every behaviour change.
How it works
Quickstart: first match in a minute
- 01
Get a key
Sign up, and the key is on the first screen. Use a he_test_ key to build without spending credits.
- 02
Make one lookup
POST /v1/lookup with a linkedin_url or a name and domain, and the fields you want.
- 03
Read the states
Each field returns verified, risky or notfound with a checked_at date. credits_charged tells you what the call cost.
Your first call
curl
curl https://api.heyenrich.io/v1/lookup \
-H "Authorization: Bearer he_test_…" \
-H "Content-Type: application/json" \
-d '{ "first_name": "Priya", "last_name": "Raman",
"domain": "northwind-traders.example", "fields": ["work_email"] }'Everything else
- API referenceEvery endpoint, request and response field, error code and rate limit.
- BulkFile format, column mapping, job states, webhooks.
- IntegrationsClay, HubSpot, n8n, Zapier, Google Sheets, with setup steps.
- API overviewCredits per endpoint, latency, sandbox keys, sub-keys.
- ChangelogDated behaviour changes, coverage refreshes, new fields.
- llms.txtThe short version for AI agents.
FAQ
Docs questions
Is there an OpenAPI spec?
Yes, at api.heyenrich.io/v1/openapi.json. It's generated from the same source as the reference, so the two can't drift.
Which languages have SDKs?
None yet. One endpoint with JSON in and out doesn't need one. The reference has curl, Node and Python samples for every call.
Where do I report a bug in the docs?
hey@heyenrich.io with the page URL. Fixes usually ship the same day.