Sender · Referral - Type B

Non-API flow

Setup overview

This guide is for partners sending leads to Konduit through a URL (non-API). Use URL parameters only for low-sensitivity tracking and product-selection fields, following the security guidance below.

  1. Share the IPs that need to be allowlisted for test and production.
  2. Konduit shares the QA URL.
  3. Send test leads to the QA URL using the allowed URL parameters.
  4. After pre-population is confirmed, Konduit shares the production URL.
  5. Use the online dashboard for lead-level data or arrange postback with Konduit.

Parameter reference (guide examples)

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.

  • Only permitted low-sensitivity fields should be passed as URL parameters; the full reference table below does not mean every field may be placed in a URL.
  • 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>
  • Field names are reproduced as supplied. The reference uses Lead_id, while the illustrative URL example uses lead_id; do not assume the two spellings are interchangeable.
  • The value for productType must exactly match the value provided by Konduit.
  • Example: <QA URL>?productType=PersonalLoan&campaign=social_fb2&sub_affiliate=2342&lead_id=185643&zip=11022&loanAmount=5000
Parameter Section

The values in this reference are illustrative examples. Actual customer information is shared privately. Inclusion here does not authorize sending sensitive values in URL query strings.

Field NamePurposeValueExample
campaigncampaign name that you want to use for trackingstringsocial_fb2
sub_affiliateaffiliate code that you want to use for trackingstring2342
Lead_idlead id that you want to trackstring185643
loanAmountAmount of loan requestedNumeric (without commas or decimals)5000
emailEmailstringjsmith@aol.com
firstNameFirst nameString 1-64John
lastNameLast NameString 1-64Smith
homePhone10 digit number8881234445
zip5 number zipNumeric (e.g. 20190)11022
statestate of leadTwo letter state codeCA, TN, etc
addressStreet addressString 1-256 (use %20 for space)2367%20SW%20St
dobDate of birthYYYY-MM-DD1990-10-31
ssnSSNLength 9 (without dashes)123224455
activeMilitaryActive Military (see valid values)YES | NONO
driversLicenseNumberDrivers License NumberLength 2-25 (without dashes and spaces)K231256
incomeTypeSource of income (see valid values)EMPLOYMENT | BENEFITSEMPLOYMENT
workCompanyNameemployer Namestring (no spaces)
incomeNetMonthlyMonthly IncomeIf:
$1,000 - $1,500 → 1500
$1,501 - $2,000 = 2000
$2,001 - $2,500 = 2500
$2,501 - $3,000 = 3000
$3,001 - $3,500 = 3500
$3,501 - $4,000 = 4000
$4,001 - $5,000 = 5000
$5,001+ = 6000
2000
incomePaymentFrequencyFrequent of payroll (see valid values)WEEKLY | BIWEEKLY |
TWICEMONTHLY |
MONTHLY
BIWEEKLY
workPhoneWork Phone (must be
different from Home, most lenders require two different phone numbers)
Numeric (without dash)2123334545
incomeNextDate1Date of next income paymentYYYY-MM-DD2024-07-19
bankAccountTypeBank account type (see valid values)CHECKING | SAVINGCHECKING
bankDirectDepositIf they want loan in a bank account (see valid values)YES | NONO
creditRatingself-reported or estimate on likely credit tier of the lead (see valid values)GREAT | GOOD | FAIR | POORGOOD
loanPurposeCustomer’s loan purpose (see valid values)DEBT_CONSOLIDATION | EMERGENCY_SITUATION | AUTO_REPAIR | MOVING | HOME_IMPROVEMENT | MEDICAL | MAJOR_PURCHASE | CREDIT_CARD_CONSOLIDATION | OTHERAUTO_REPAIR
unsecuredDebtSend "YES" if the customer
has more than $10,000 in unsecured debt
YES | NOYES
autoTitleSend "YES" if the customer
has a free and clear title to a
vehicle under their name.
Send “NO” if the customer
does not
YES | NOYES
bankAbaBank routing numberNumeric (without dash or spaces)044000023
bankAccountNumberBank account numberNumeric (without dash or spaces)2356432
productTypeOffer the lead is requesting (required if Konduit configured more than one offer)stringPersonalLoan

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.

Example URL format:

basic
https://yourdomain.com?param1=value1&param2=value2

Expected response:

basic
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 nameTypeDescriptionExample
lead_idStringLead ID for the transaction12345
amountFloatTransaction amount1.00
timestampdatetimeDate and time of the event01/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:

Webhook payload:

json
{
  "lead_id": "12345",
  "amount": "100.00",
  "timestamp": "01/01/2024 01:01:01"
}

The success or error response can be customized; below is the standard response we expect. Expected webhook success response:

HTTP Status Code: 200 OK

Response body (JSON):

json
{
  "status": "success",
  "message": "Transaction processed successfully."
}

Expected error response example:

HTTP Status Code: 400 Bad Request

Response body (JSON):

json
{
  "status": "error",
  "message": "<Reason of Error>"
}