All integrations
Data in and out
Inbound lead API
Lead vendors and landing pages post real-time leads straight into a campaign, each with its own key.
- Connects by
- POST /api/leads/inbound
- Set up by
- Agency admin, then the vendor
- In Vora
- Leads, into the vendor's campaign
What it does in Vora
- Checks every lead like an imported row: phone, time zone, duplicates, do-not-call and consent
- Adds it to the vendor's campaign and assigns it at once to an agent licensed in the lead's state
- Puts real-time leads at the front of the dial queue
- Accepts consent certificate URLs or IDs with each lead
Setting it up
- 1
An admin creates a key for the vendor and shares it over a secure channel.
- 2
The vendor posts one lead per request as JSON, up to 16 KB.
- 3
Vora answers 201 with the lead id, or 200 if an open lead with that phone already exists.
Guardrails
What Vora holds back, checks or refuses, so this connection never becomes the weak point.
- A vendor key can only send leads. It cannot read anything.
- Responses never repeat the lead's details back.
- A lead without a consent certificate is added but cannot be called until consent is on file.
Inbound lead API is a trademark of its owner. Listing it here does not imply a partnership or endorsement.
Bring your agency onto Vora
Book a demo. We will walk your team through Vora, then set up your carriers, commission grid and hierarchy with you.