form.*, scoring.*, attribution.*).
Adaptive Schema & Zero Data Loss Guarantee:
The parameters below represent our recommended canonical field names. However, you do not need to rewrite your platform’s existing JSON format.
The parameters below represent our recommended canonical field names. However, you do not need to rewrite your platform’s existing JSON format.
- Auto-Adaptation: 3i’s multi-pass ingestion engine uses proprietary semantic resolution to automatically align your custom field names with our platform schema (e.g.
phone_num→phone,coverage_requested→coverage_amount,dob→date_of_birth,zip→zipcode). - Unmapped Data Preservation: Any question, score, or custom parameter unique to your system is never dropped—it is automatically swept into
custom_fieldsand displayed in the agent’s CRM drawer under Vendor Data.
Primary Contact Fields
string
required
The full contact name (e.g.
"Marcus Vance"). Alternatively, provide first_name and last_name; 3i will combine them automatically into the display name.Accepted aliases: fullname, full_name, contact_name, lead_name.string
The contact’s first name.
string
The contact’s surname. Automatically combined with
first_name if name is omitted.Accepted aliases: lastName, surname, family_name, lname.string
The primary telephone number. Accepts standard E.164 (
+15125550188), punctuated US format ((512) 555-0188), or 10 raw digits (5125550188). 3i automatically strips punctuation and normalizes to a clean 10-digit format for carrier dialing.Accepted aliases: phone_number, telephone, tel, mobile, cell, contact_phone.string
Primary email address. Automatically trimmed and stored lowercase.Accepted aliases:
email_address, contact_email, e_mail, lead_email.Address & Geographic Fields
string
Street address (e.g.
"1204 Pecan Grove Rd").Accepted aliases: street, street_address, address1.string
City or municipality name (e.g.
"Austin").Accepted aliases: town, municipality.string
US state. Accepts 2-letter abbreviation (Accepted aliases:
TX, FL, CA) or full name (Texas, Florida).Automatic Timezone Detection: 3i automatically infers and assigns the prospect’s local timezone based on the
state code or telephone area code.st, region, province.string
5-digit postal code (e.g.
"78704"). Automatically coerced to a clean string format.Accepted aliases: zip, zip_code, postal_code.string
County or parish name (e.g.
"Travis").Accepted aliases: parish.Demographics & Language
string
Date of birth formatted as
YYYY-MM-DD or standard US format MM/DD/YYYY (e.g. "1963-04-12").Accepted aliases: dob, DOB, birth_date, birthdate.integer
Contact’s age in years. Validated strictly between 18 and 120 to prevent coverage amounts or zip codes from polluting age fields.
string
Contact gender:
Male or Female. Values like m, f, male, or female are normalized automatically to canonical Male or Female.string
Primary preferred language (e.g.
"English", "Spanish").Accepted aliases: lang, preferred_language.Notes & Custom Fields
string
Free-text briefing notes for the agent. If you send multiple note fields (
comments, remarks, additional_info, description), 3i automatically concatenates them using a | separator.object
A flexible JSON object holding any partner-specific metadata, external database identifiers, call recording URLs, or quiz answers.3i automatically preserves all custom properties and renders them inside the CRM Lead Details drawer under Vendor Data: