Ten short screens. Pick the product and the pool, set the count, then your account, where the leads land, and the card. The order starts filling as soon as it is paid.
Where your leads land. New or already with us, same box.
Already have an account?
Saved to your account, so we only ask once. We only send leads from these states.
A webhook on your own system. It is where we send the leads you buy.
This is exactly what we POST to that URL. Copy it into your system so the fields line up before the first lead arrives.
{
"event": "lead.assigned",
"lead": {
"id": "3f9c1a7e-2b40-4d18-9a55-6e0d7c8b1f22",
"type": "mortgage_protection",
"first_name": "VC DEMO",
"last_name": "LEAD",
"phone": "+16155550142",
"email": "test-lead@example.com",
"state": "TN",
"zip": "37013",
"age_range": "Under 60",
"beneficiary": "Spouse or partner",
"payload": {
"Age Range": "Under 60",
"Coverage Target": "$425,000",
"Coverage Selected": "Full remaining mortgage balance",
"Monthly Payment": "$3,700",
"Remaining Mortgage": "$425,000",
"Beneficiary": "Spouse or partner",
"Zip": "92337",
"Address": "123 Example St",
"Confirmed Non-Landline": true
}
},
"delivered_at": "2026-09-08T14:03:11.204Z"
}
Every lead we POST carries x-sakredcrm-signature: sha256=<hex>: an HMAC-SHA256 of the raw request body, keyed on a signing secret that is yours alone. Check it and your intake can refuse anything that didn’t come from us. Verify against the raw body, before your framework parses it: re-serialising the JSON gives a different byte string and fails every check. Your secret, and a three-line snippet, are on your delivery settings page once you’re in. Nothing about the body changed: if you’re not ready to verify, your endpoint keeps working exactly as it does today.
We have emailed you the account details.