One JSON POST per lead. Mapped to your CRM.
Each lead is posted to an HTTPS endpoint you give us as soon as it passes its checks and matches your filters.
How the webhook works
When a lead clears all 8 checks and matches your order, we send one POST with a JSON body to your endpoint. The design target from form submit to POST is under 60 seconds.
- Endpoint: any HTTPS URL: your CRM's inbound webhook, a Zapier Catch Hook or your own server.
- Authentication: set up with you during onboarding to suit your endpoint, for example a secret header or a token in the URL.
- Response: return a
2xxto accept. Tell us how you want failures handled and who should be alerted. - Format: JSON by default. We can post form-encoded fields or your CRM's own field names instead.
Test first. Before any real lead is delivered we post clearly marked test records ("test": true) so you can check mapping, routing and duplicate handling.
# Request POST /inbound HTTP/1.1 Content-Type: application/json User-Agent: lead-delivery # Your response HTTP/1.1 200 OK { "received": true }
Example lead JSON
Illustrative values. The person below is made up.
{
"lead_id": "ld_sample_0001",
"test": true,
"delivered_at": "2026-01-15T15:04:09Z",
"vertical": "debt_settlement",
"tier": "exclusive",
"contact": {
"first_name": "Sample",
"last_name": "Consumer",
"phone": "+15555550100",
"email": "sample@example.com",
"state": "TX"
},
"debt": {
"debt_amount_band": "25000-29999",
"debt_amount_min": 25000,
"debt_type": "credit_card",
"payment_status": "behind",
"months_behind": 3,
"income_status": "employed",
"in_program": false
},
"consent": {
"text": "(exact consent language shown to the consumer)",
"timestamp": "2026-01-15T15:03:41Z",
"ip": "203.0.113.24",
"page_url": "https://debtclearlife.com/",
"trustedform_cert_url": "https://cert.trustedform.com/(certificate id)"
}
}
Field schema
| Field | Type | Values / notes |
|---|---|---|
| lead_id | string | Unique per lead. Use it for returns and duplicate checks. |
| test | boolean | true only on test records. |
| delivered_at | ISO 8601 | UTC time of the POST. |
| vertical | enum | debt_settlement, credit_card_debt, debt_consolidation, tax_debt, private_student_loan |
| tier | enum | exclusive, semi_exclusive, shared |
| contact.first_name / last_name | string | As entered by the consumer. |
| contact.phone | string | E.164 format. |
| contact.email | string | As entered by the consumer. |
| contact.state | string | Two-letter code, 50 states plus DC. |
| debt.debt_amount_band | string | Self-reported total unsecured debt band, in dollars. |
| debt.debt_amount_min | integer | Lower edge of the band. This is what your minimum-debt filter uses. |
| debt.debt_type | enum | credit_card, personal_loan, medical, tax, private_student_loan, other |
| debt.payment_status | enum | current, behind |
| debt.months_behind | integer | 0 when current. |
| debt.income_status | enum | employed, self_employed, retired, benefits, none |
| debt.in_program | boolean | Consumer says they are already in a debt relief program. |
| consent.text | string | Exact consent language shown. |
| consent.timestamp | ISO 8601 | When the consumer submitted the form. |
| consent.ip | string | IP address of the submission. |
| consent.trustedform_cert_url | URL | TrustedForm certificate. Claim it in your own TrustedForm account if you retain certificates. |
Field names are finalized with you during onboarding and can be renamed to match your CRM. Store the consent fields with the contact record: you will want them if a consumer or regulator ever asks how you got the number.
Works with the systems debt relief floors already run.
These are delivery targets we map the webhook to. They are not partnerships or endorsements.
DebtPayPro
Post leads straight into DebtPayPro as new contacts with debt fields mapped.
Forth CRM
Deliver into Forth with the debt band, debt type and consent fields mapped.
Salesforce
Create Leads through web-to-lead, a REST endpoint or middleware.
HubSpot
Create contacts with custom debt properties and trigger your workflows.
Zoho CRM
Push leads into the Leads module with field mapping.
GoHighLevel
Inbound webhook into a workflow: contact, pipeline stage, first SMS or call task.
LeadsPedia
Post into your LeadsPedia campaign for onward routing and reporting.
Zapier
Catch the webhook in Zapier and route it anywhere it connects to.
Generic webhook
A JSON POST to any HTTPS endpoint you control.
A minimal receiver
Accept the POST, check your shared secret, de-duplicate on lead_id, store the consent block and answer quickly. Do the slow work (CRM writes, SMS, dialer push) after you respond.
Then call fast. See speed to contact and CRM integrations for routing ideas.
app.post('/inbound', express.json(), (req, res) => { // 1. shared secret agreed at onboarding if (req.get('X-Auth-Token') !== process.env.LEAD_TOKEN) return res.status(401).end(); const lead = req.body; // 2. never work test records if (lead.test) return res.json({ received: true }); // 3. answer first, then do the slow work res.json({ received: true }); queue.add({ id: lead.lead_id, lead }); });
Integration questions.
Do I need a developer?
Can you post in my CRM's format instead?
How do I test before going live?
Ready to see it on a call?
Fifteen minutes. We will walk through pricing, which states and filters are live, and how delivery into your CRM works.