Push everything to your stack
Create lists, leads and campaigns through a REST API, and send events to your CRM or automation tool through webhooks.
curl -H "X-API-KEY: YOUR_API_KEY" \
"https://YOUR_HOST/api/v1/lead-lists/LIST_ID/leads"
# {
# "data": [ ... ],
# "nextCursor": "..."
# }Placeholders only. Create a key in your settings and read the reference at /api-docs.
Your CRM does not see what happens on LinkedIn
Replies, accepted invites and opt-outs stay inside the outreach tool unless someone copies them out. Lists made elsewhere have to be imported by hand.
An API and webhooks, documented
Read and write your data over a public REST API, and receive events at your own endpoint. Every call is in the OpenAPI reference.
How it works
Create an API key
Issue a key in your settings. Only a hash of it is stored. Send it in the X-API-KEY header.
Call the API
List accounts, manage lead lists, fields and leads, mark opt-outs, and create, start, pause and duplicate campaigns.
Subscribe to events
Add an https webhook URL, choose the events and add custom headers for your own authentication.
Watch the deliveries
Every delivery is logged. Failed ones are retried on a schedule, and you can send a test event whenever you like.
What it does
REST API under /api/v1
Accounts, lead lists with their fields and leads, single leads, opt-out, campaigns and webhooks.
API keys, stored hashed
Keys are shown once when you create them. Only a hash is kept on our side.
OpenAPI reference
A public reference at /api-docs lists every endpoint, so you can read it without signing in.
Events to choose from
Replies, accepted and rejected invites, sent messages, failed sends, completed sequences, opt-outs, disconnected accounts and campaign pauses and resumes.
Custom headers, stored encrypted
Add your own headers to every delivery, such as an authorization token. They are stored encrypted.
Delivery log, retries, test-send
See each delivery and its result. Failed deliveries are retried up to five times, from one minute to twelve hours later.
Questions
Is there a public API?
Yes. It lives under /api/v1 and covers accounts, lead lists, leads, opt-outs, campaigns and webhooks. You authenticate with an API key in the X-API-KEY header.
Where is the reference?
At /api-docs, an OpenAPI reference you can read without signing in.
How do I secure a webhook endpoint?
Add a custom header, for example a secret token, to the webhook. We send it with every delivery and store it encrypted. Webhook deliveries themselves are not signed.
What happens when my endpoint is down?
Deliveries are logged and retried up to five times, from one minute to twelve hours later. A webhook that keeps failing for three days is switched off.