Affiliate Leads
Two Affiliate Integration Paths
1. API-based (server-to-server)
Affiliates POST JSON leads to:
POST https://leads.businessdebtinsider.com/api/affiliate-leads/submit
Header: X-API-Key: affk_...
2. Landing page (send traffic to us)
Affiliates send traffic to any LP with URL params:
https://leads.businessdebtinsider.com/lp/rich-mca-debt-relief?aff=AFFILIATE_ID&click_id=XYZ&sub1=...&sub2=...&sub3=...
Visitor fills our form → lead is tagged with their affiliate_id + subs.
Both paths show leads in this table and in the affiliate's portal at /affiliate/.
Show example payload
curl -X POST https://leads.businessdebtinsider.com/api/affiliate-leads/submit \
-H "Content-Type: application/json" \
-H "X-API-Key: affk_..." \
-d '{
"first_name": "John",
"last_name": "Doe",
"email": "[email protected]",
"phone": "5551234567",
"company_name": "Acme LLC",
"debt_amount": "50000",
"has_mca": "Yes",
"state": "FL",
"sub_id": "mca-list-a",
"click_id": "abc123"
}'
Zapier Webhook
Every affiliate lead is forwarded to this URL. Leave blank to disable.
Affiliates
Each affiliate has an API key (for sending us leads), an optional postback URL (for receiving conversions),
and an optional login PIN (for access to their portal at /affiliate/).
Postback URL supports {clickid}, {sub1}, {sub2}, {sub3},
{payout}, {event}.
| Label | Affiliate ID | API Key | Postback URL | Portal PIN | Status | Last Used | Actions |
|---|---|---|---|---|---|---|---|
Leads
| Created | Affiliate | Source | Name | Phone | Debt | Click ID | Sub1 | Sub2 | Sub3 | Actions | |
|---|---|---|---|---|---|---|---|---|---|---|---|