Authentication
curl https://api.leadey.ai/v1/leads \
-H "Authorization: Bearer lk_live_..."Create a named key in Settings → API Keys. The key is shown in full exactly once; after that you'll see a prefix and the last four characters. Keys are scoped to one organisation and can be revoked instantly.
Endpoints
Account · Companies · Contacts · Pipelines · Reference
Metrics
Group any metrics endpoint by day, week, rep or campaign, with a timezone parameter. Week keys are ISO, such as 2026-W31.
The API and the interface share the same metric libraries, so a figure in your warehouse and a figure on a rep's screen cannot disagree. Sit rate is attended divided by attended plus no-show, and meetings with no attendance recorded are excluded from the denominator rather than quietly counted as no-shows.
Webhooks
Every campaign has a tokenised webhook URL that accepts leads from anywhere. It ships with 20+ field aliases, so payloads using full_name, work_email or job_title map with no configuration.
Any workflow can fire a webhook node at a URL of your choosing with the lead payload.
Why read-only
The API is read-only by design. There is no user identity behind an API key, which means no owner for a created record, no permission scope to enforce, and no audit trail worth the name. Rather than pretend otherwise, writes go through the interface and the campaign webhooks, where those things exist.