API keys, the public API, and webhooks to your systems
Three related things, all under Settings: keys that let outside software talk to your account, the API those systems call, and webhooks that push events out to you. You don't have to be technical to set these up — but the person on the other end usually is, and there's a full reference for them.
API keys
Settings → Integrations & API → API keys (Admins only). Create a key per system, so you can revoke one without breaking the rest. For each key you choose what it's allowed to do:
- Read data — look at leads, stats, and settings.
- Send & change data — what a lead source needs to post leads in.
- Manage account setup — can change integrations, branding, and data-deletion settings. Only give this to systems you fully trust.
You can also attach a default campaign to a key, so leads arriving on that key go to that campaign without the sender specifying it. The key itself is shown once, at creation — copy it then.
The public API
The API covers the whole operating loop: send leads in, read your stats, create and activate destinations and campaigns, manage your do-not-call list, and handle consumer data requests. The complete reference and a step-by-step quickstart live at docs.lead2inbound.com — hand that to your developer.
Plan note: the API is a Growth-plan feature. On Starter, two things still work with a key so lead flow and compliance are never blocked: posting leads in, and managing your do-not-call list and consumer data requests.
Webhooks — us telling your systems
A webhook is a message we send to a web address of yours the moment something happens, so your CRM or dashboard doesn't have to keep asking. Set them up under Settings → Notifications → Notifications to your systems. Pick which events you want:
- A new lead arrives
- A lead qualifies on a call
- A call finishes
- A caller is connected to a buyer
- A campaign finishes
Each message is signed so your side can prove it came from us, and failed deliveries retry on a backoff before giving up. There's a Send test button so your developer can wire it up without waiting for a real call. Creating webhooks is a Growth-plan feature; existing ones keep delivering, and you can always view or delete them.
Webhooks vs postbacks — not the same thing
Webhooks push events out from us to you. A postback is the opposite: your buyer's routing platform calling in to tell us what a transferred call paid. Postbacks are set up on the Destinations page — see Tracking revenue.