← All lead types HELOC lead post · Field reference · V1 · October 2026 Download PDF

LeedWallet · HELOC lead post

Field reference

The 31 fields LeedWallet posts to your endpoint for each HELOC lead: name, type, allowed values and format.

Buying DSCR leads too? DSCR posts a different set of fields. See the DSCR field reference.

  • Fields31
  • MethodHTTP POST
  • Bodyapplication/json
  • ValuesJSON strings

1Overview

How a lead gets from LeedWallet into your system, in order.

  1. Provide your endpointGive LeedWallet the URL that will receive HELOC leads and any authentication header it requires. This is configured at onboarding, separately from any DSCR delivery.
  2. Accept the postEach lead arrives as one HTTP POST with a JSON body of 31 fields. Every value is a string. See section 2.
  3. Map the fieldsMatch each field to your system using the tables in section 5. Convert numeric and yes/no values, and the coded list values, on your side.
  4. Store the consent fieldsKeep tcpa_text, ip_address, user_agent, jornaya and trustedFormCertUrl with the lead record. See section 5.6.
  5. Confirm receiptReturn a 2xx HTTP status. Use transaction_id to reject duplicates.

2Delivery format

Transport and formatting rules that apply to every field in the post.

Transport
One HTTP POST per lead with a JSON body (Content-Type: application/json). Endpoint URL and any authentication headers are configured per buyer at onboarding.
Field presence
All 31 fields are present on every post. A field that does not apply to the lead is sent as an empty string, not null and not omitted.
Value types
Every value is sent as a JSON string, including numeric fields. Numbers contain no currency symbols or thousands separators. Yes/no fields contain the lowercase strings yes or no, not booleans. Some list values are codes, such as sole_owner and full_time; map them to your own labels.
Field names
Field names are case-sensitive. All are snake_case except trustedFormCertUrl.
Timestamp
The HELOC post carries no submission timestamp. Record the time you receive it.
Response
Return a 2xx HTTP status to confirm receipt.
Duplicate handling
transaction_id is unique per lead. Use it for duplicate checks.

3Field types

Type labels used in section 5, as defined by the LeedWallet delivery platform.

TypeMeaning
TextFree-form string. Most are short; user_agent and tcpa_text can exceed several hundred characters.
EmailEmail address, format-validated at submission.
Phone10-digit US number.
StateTwo-letter USPS abbreviation.
Postal codeFive-digit ZIP. Keep it as text so leading zeros survive.
IP addressIPv4 dotted quad, e.g. 203.0.113.42. Store as text.
NumericDigits with an optional decimal point (123, 12.34). No symbols or separators. Sent as a string.
ListOne of the allowed values, spelled and cased as shown.

4Conditional fields

2 fields

Two fields carry a value only when existing_mortgage has a specific value. Otherwise they arrive as an empty string. Fields not listed here are not tied to another field's value.

WhenThese fields are populatedOtherwise
existing_mortgage is one or tworemaining_mortgage_primaryEmpty when existing_mortgage is none.
existing_mortgage is tworemaining_mortgage_secondaryEmpty when existing_mortgage is none or one.

5Fields

25 underwriting · 6 consent & delivery

Six groups. Field names are exactly as posted. List fields contain one of the values shown; all other types show an example value. Fields whose value depends on another field are listed in section 4.

5.1Borrower contact

9 fields

Borrower name, contact details and the property address.

FieldType & formatDescription
first_nameText
ExampleDana
Borrower's first name.
last_nameText
ExampleWhitfield
Borrower's last name.
emailEmail
Exampledana.whitfield@example.com
Borrower's email address. Format-validated at submission.
mobilePhone
Example(614) 555-0187
Borrower's mobile number, 10-digit US. Remove formatting if your system stores digits only.
date_of_birthText
Example04/18/1971
Borrower's date of birth as entered, MM/DD/YYYY. May be empty.
addressText
Example2217 Linden Ave
Street address of the property as entered on the form.
cityText
ExampleColumbus
City as entered on the form.
stateState
ExampleOH
Two-letter USPS abbreviation (CA, NY, FL).
zip_codePostal code
Example43209
Five-digit ZIP. Store as text to preserve leading zeros.

5.2Loan request

3 fields

Line amount, what the funds are for, and the credit band.

FieldType & formatDescription
loan_amountNumeric
Example75000
Requested line amount in USD. Digits only, no currency symbol or commas.
loan_reasonList
Allowed values
  • Home improvement
  • Pay off debt
  • Buying another property
  • Life Event / Unexpected Bills
  • Business expenses
What the borrower plans to use the funds for.
credit_scoreList
Allowed values
  • Excellent (720+)
  • Good (680-719)
  • Fair (640-679)
  • Poor (639 and below)
Credit band as reported by the borrower, not a credit pull. Delivered leads are Fair (640+) or better; Poor is listed for schema completeness. These bands differ from the DSCR bands.

5.3Property

5 fields

The home the line would be secured by.

FieldType & formatDescription
property_useList
Allowed values
  • Primary
  • Secondary
  • Investment
How the borrower uses the property.
property_typeList
Allowed values
  • Single Family
  • Multi Family
  • Townhouse
  • Condo
  • Manufactured or Mobile
Property type as selected on the form.
estimated_property_valueNumeric
Example420000
Borrower's estimate of the property's current value in USD.
ownership_typeList
Allowed values
  • sole_owner
  • joint_owner
  • trust
  • llc
  • corporation
How title is held: by the borrower alone, jointly, or through a trust or entity.
property_for_saleList
Allowed values
  • yes
  • no
Whether the property is currently listed for sale.

5.4Existing mortgages

3 fields

Liens on the property today. With estimated_property_value they give you equity and CLTV.

FieldType & formatDescription
existing_mortgageList
Allowed values
  • none
  • one
  • two
Number of mortgages currently on the property.
remaining_mortgage_primaryNumeric
Example185000
Balance on the first mortgage in USD. Empty when existing_mortgage is none.
remaining_mortgage_secondaryNumeric
Example40000
Balance on the second mortgage in USD. Empty unless existing_mortgage is two.

5.5Income & background

5 fields

Income, employment and credit history as reported by the borrower.

FieldType & formatDescription
annual_incomeNumeric
Example96000
Borrower's annual income in USD as reported.
employment_statusList
Allowed values
  • full_time
  • part_time
  • self_employed
  • retired
  • unemployed
Borrower's employment status.
proof_of_incomeList
Allowed values
  • tax_returns
  • bank_statements
  • profit_loss
  • assets
  • not_sure
How the borrower would document income. May be empty.
active_militaryList
Allowed values
  • yes
  • no
Whether the borrower is on active military duty.
bankruptcyList
Allowed values
  • yes
  • no
Whether the borrower reports a bankruptcy.

5.6Consent, compliance & delivery

6 fields

Consent records and identifiers for the lead.

FieldType & formatDescription
tcpa_textText
ExampleBy clicking Submit, I agree to receive calls and text messages from LeedWallet and up to three lending partners at the number provided, including via automated dialing technology. Consent is not a condition of purchase.
The exact consent language the borrower agreed to at submission. Store with the lead record.
ip_addressIP address
Example203.0.113.42
Borrower's IP address at submission.
user_agentText
ExampleMozilla/5.0 (iPhone; CPU iPhone OS 17_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.5 Mobile/15E148 Safari/604.1
Browser user-agent string captured at submission.
jornayaText
Example3f2a9c1e-7b4d-4e8a-9f01-2c6d5b8a1e47
Jornaya LeadiD token for independent consent verification.
trustedFormCertUrlText
Examplehttps://cert.trustedform.com/6f1c0a9e2b7d4c3a8e5f1b2d9c0a7e6f4d3b2a10
TrustedForm certificate URL. Note the camelCase name, which differs from the DSCR post. Retain it in your TrustedForm account promptly; unclaimed certificates expire.
transaction_idText
Example8c41f2e7-9a3b-4d6e-b5c0-72f1a9e3d4b8
LeedWallet's unique ID for the lead. Use it for duplicate checks and when referencing the lead with LeedWallet.

No field matches that search.

6Sample post

Example values

Example values only: one existing mortgage, so remaining_mortgage_secondary is empty.

{  "first_name": "Dana",  "last_name": "Whitfield",  "email": "dana.whitfield@example.com",  "mobile": "(614) 555-0187",  "date_of_birth": "04/18/1971",  "address": "2217 Linden Ave",  "city": "Columbus",  "state": "OH",  "zip_code": "43209",  "loan_amount": "75000",  "loan_reason": "Home improvement",  "credit_score": "Good (680-719)",  "property_use": "Primary",  "property_type": "Single Family",  "estimated_property_value": "420000",  "ownership_type": "joint_owner",  "property_for_sale": "no",  "existing_mortgage": "one",  "remaining_mortgage_primary": "185000",  "remaining_mortgage_secondary": "",  "annual_income": "96000",  "employment_status": "full_time",  "proof_of_income": "tax_returns",  "active_military": "no",  "bankruptcy": "no",  "tcpa_text": "By clicking Submit, I agree to receive calls and text messages from LeedWallet and up to three lending partners at the number provided, including via automated dialing technology. Consent is not a condition of purchase.",  "ip_address": "203.0.113.42",  "user_agent": "Mozilla/5.0 (iPhone; CPU iPhone OS 17_5 like Mac OS X) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.5 Mobile/15E148 Safari/604.1",  "jornaya": "3f2a9c1e-7b4d-4e8a-9f01-2c6d5b8a1e47",  "trustedFormCertUrl": "https://cert.trustedform.com/6f1c0a9e2b7d4c3a8e5f1b2d9c0a7e6f4d3b2a10",  "transaction_id": "8c41f2e7-9a3b-4d6e-b5c0-72f1a9e3d4b8"}

The borrower, property, tokens and consent text above are placeholders and do not describe a real lead.