Connect your lead flow once. Every lead is priced, checked and delivered automatically.
VeryBookedAI buys exclusive leads for local service businesses: 336 services in 12 countries. Send each request through our ping-post API. You see the price before any personal data leaves your system, and every lead you sell goes to one business only.
A ping-post exchangeLIVE PING-POSTTwo ways to work with us
Most partners sell leads through the API. If you work with local businesses rather than with the people hiring them, introduce those businesses instead.
API STREAM01Lead sellers
Lead generation companies, media buyers and quote or comparison sites that collect consent-based requests for local services.
- A price for every lead from the ping, before you send personal data
- The payout on each post is the price its ping quoted
- 336 services in 14 categories
- Signed, encrypted delivery with the consent record kept alongside each lead
B2B REFERRAL02Referral partners
Agencies, accountants, software providers and suppliers who already work with local businesses.
- Introduce businesses that want exclusive local leads
- Claiming a VeryBookedAI profile is free for the business
- Businesses pay per exclusive lead from a prepaid balance
- Your commission terms are agreed in writing before your first referral
What the integration automates
Two endpoints do the work on every request. This is what they do today.
- A price before personal data
- A ping carries the service, postal code, country and urgency, nothing that identifies a person. It returns a price and a transaction ID held for 15 minutes.
- Payout confirmed on delivery
- Post the contact details against that transaction ID. The response returns the lead ID and the payout, which is the price the ping quoted.
- Encrypted on arrival
- Contact details are sealed with AES-256-GCM envelope encryption before they are stored.
- Consent evidence kept with the lead
- The time of consent and the exact wording your visitor agreed to are hashed into a consent record. TrustedForm and Jornaya certificates are stored with the lead.
- Signed and replay-protected
- Posts are signed with HMAC SHA-256 over a timestamp and the body. A signature more than five minutes old is refused.
- Errors your code can act on
- A rejected request names the field and the reason, and successful responses carry a Server-Timing header so you can track latency.
bidPricepayoutenvelopeconsent.acknowledgedAtX-Signature-SHA256errors[].pathHow it works
01ApplyTell us who you are, where your traffic comes from and which categories you can supply.02IntegrateOnce you are approved we share your signing secret. Map your form to the ping and the post, and test against the documented responses.03Send leadsSend a ping for each request, a post for each lead you want to sell, and keep the lead ID and payout from every response.
Start with the documentation, or apply now
The API reference lists every field, header and error message the two endpoints return.