The Konduit exchange has two sides. Senders submit referrals. Receivers publish what they will buy and respond to what they are sent. Every call is JSON over HTTPS.
Sender
Indicate interest anonymously, then submit a full referral as Type A or Type B.
Receiver
Define the product you want, the senders allowed to reach you, and how you respond to each referral.
Sender
Referral intent
Partners can indicate interest based on anonymous or pseudonymous information. Identity and supporting details are disclosed progressively after the customer chooses to proceed.
Accept: application/json Authorization:To be issued by Konduit Channel: API Content-Type: application/json; charset=utf-8 Institution-Id: LGR Partner-Id:To be issued by Konduit
Headers – Prod
Accept: application/json Authorization:To be issued by Konduit Channel: API Content-Type: application/json; charset=utf-8 Institution-Id: LGR Partner-Id:To be issued by Konduit
This guide is for partners sending leads to Konduit through a URL (non-API). Use URL parameters only for the low-sensitivity tracking and product-selection fields listed below; they will be pre-populated on the landing page.
Share the IPs that need to be allowlisted for test and production.
Konduit shares the QA URL.
Send test leads to the QA URL using the allowed URL parameters.
After pre-population is confirmed, Konduit shares the production URL.
Use the online dashboard for lead-level data or arrange postback with Konduit.
URL parameters (pre-populating lead info)
Never place sensitive information in query strings. Do not send SSNs, driver’s license numbers, dates of birth, bank routing numbers, bank account numbers, or other sensitive values in URL parameters. Query strings can be exposed through browser history, logs, referrer headers, and analytics. Collect sensitive values only through the secure HTTPS form or authenticated API.
No integration is needed to prefill the low-sensitivity fields below; pass them as URL parameters.
If you do not have a value, omit the parameter rather than sending a default. The lead can complete the field on the landing page.
Format: <URL shared by Konduit>?<FieldName1>=<Value1>&<FieldName2>=<Value2>
For prefill to work, use the exact capitalization shown below. For example, productType works but producttype does not.
The value for productType must exactly match the value provided by Konduit.
Offer the lead is requesting (required if Konduit configured more than one offer)
string
PersonalLoan
loanAmount
Requested loan amount
numeric, without commas or decimals
5000
zip
Five-digit ZIP code
numeric
11022
Postback
Setup requirement: These examples are illustrative. Konduit provides partner-specific credentials, authentication, signature, and replay-protection requirements directly during setup. Partners must complete and validate that setup before production. lead_id must be an opaque identifier with no customer data.
The dashboard provides lead-level conversion data in real time that can be downloaded as CSV. URL and webhook postback are also available on request.
URL postback
You can receive data through a URL in a GET request. Provide your URL in the format below.
HTTP Status Code: 200 OK
Upon successful receipt of the data, your system should return a 200 OK status to
confirm that the postback was processed correctly.
Available parameters:
Parameter name
Type
Description
Example
lead_id
String
Lead ID for the transaction
12345
amount
Float
Transaction amount
1.00
timestamp
datetime
Date and time of the event
01/01/2024 01:01:01
Webhook postback
To set up a webhook postback, provide the endpoint URL where you want to receive data. Konduit will send the following body:
{
"status": "error",
"message": "<Reason of Error>"
}
Receiver
Demand listing
A receiver defines a referral program. The sender sees the product, requirements, price, service metrics and anonymized receiver reputation — but not necessarily the receiver's identity.