GENERAL Post Instructions

General Bucket

The following is a list of fieldnames that we accept for this vendor. Anything else will be rejected or not inserted into the system.

If the server detects data via the POST method it will assume all data is coming in from that method rather than GET, however the vendor_id and post_key GET Parameters must always appear in the URL.

Required Fields

You must provide one valid phone number or e-mail address for a lead to be accepted!

Valid Field Types

  • Phones: Phone numbers will be stripped of non numeric digits and truncated to 10 digits from right to left
  • Emails: E-mails will be validated or ignored.
  • Boolean Fields: Values must be 0 or 1, blank strings are considered null and not set.
  • Gender: M or F, any other letters will be truncated.
  • State, State of Birth: Provide 2 Letter State Abbreviation.
  • Language: 1: English, 2: Spanish.
  • Datetime Fields: Date time fields will be converted from almost any format into the following format: Y-m-d H:i:s
  • Date Fields: Date will be converted from almost any format into the following format: Y-m-d
  • Time Fields: Dates will be converted from almost any format into the following format: H:i:s
  • System Field ID's: Must be numeric reference to an ID in TLDCRM. When using the uploader, you will be asked to map unique data via dropdowns.

Time Zone Conversion

Any and all Date Time formatted fields will be converted to the accounts default timezone: US/Eastern

SSL / HTTPS (Secure Sockets Layer)

If you have problems sending to our lead post over SSL (HTTPS), you can try Non-SSL (HTTP). We do NOT recommend this method and prefer you ALWAYS use HTTPS.

POST URL: https://pba.tldcrm.com/post?vendor_id=14962&post_key=0c527812043576441927a488cbe083b9

Lead Results Log: https://pba.tldcrm.com/public/vendors?vendor_id=14962&post_key=0c527812043576441927a488cbe083b9 WARNING! DO NOT POST TO THE RESULTS LOG!

The Results Log will give you the last 100 results for this vendor along with its status, lead ID and whether it posted to this vendor's dialer as well as complete debugging information to make sure your mapping was correct. Please do NOT Post data to the results log.

Vendor ID: 14962

Post Key: 0c527812043576441927a488cbe083b9

Method: HTTP POST

Response Format: TEXT

Quick VICIDial Webform Integration

If you are sending data via VICIDial Webform, you can use this link in the Webform area

VARhttps://pba.tldcrm.com/post?vendor_id=14962&post_key=0c527812043576441927a488cbe083b9&phone=--A--phone_number--B--&phone2=--A--alt_phone--B--&phone3=--A--address3--B--&email=--A--email--B--&first_name=--A--first_name--B--&middle_name=--A--middle_initial--B--&last_name=--A--last_name--B--&address=--A--address1--B--&address2=--A--address2--B--&city=--A--city--B--&state=--A--state--B--&zipcode=--A--postal_code--B--&dob=--A--date_of_birth--B--&gender=--A--gender--B--&reference_id=--A--lead_id--B--

Click the Above to Copy to Clipboard and Paste into your VICIDial Campaign Webform. Copy it EXACTLY as is, make sure no spaces were inserted before or after the URL. Also Make SURE the VAR is preset before the URL otherwise the variables will not work

Response Codes:

CodeResultDescription
1successSuccess
2successAdded new notes, policies and dependents to existing lead.
3successUpdated lead.
4successUpdated lead and added new notes, policies and dependents to existing lead.
5successAdded new policies and dependents to existing lead.
6successAdded new notes and dependents to existing lead.
7successAdded new notes and policies to existing lead.
8successAdded new notes existing lead.
9successAdded new policies to existing lead.
10successAdded new dependents to existing lead.
11successUpdated lead and added new policies and dependents to existing lead.
12successUpdated lead and added new notes and dependents to existing lead.
13successUpdated lead and added new notes and policies to existing lead.
14successUpdated lead and added new notes existing lead.
15successUpdated lead and added new policies to existing lead.
16successUpdated lead and added new dependents to existing lead.
91failPassthrough vendor is not part of the allowed passthrough vendors.
92failPassthrough vendor is not part of the allowed passthrough groups.
93failVendor passthrough not enabled for this vendor.
94failVendor does not exist.
96failPhone and Email not Provided or Mapped.
97failNo Post Key provided for Vendor.
98failInvalid Post Key for Vendor.
99failNo Vendor Selected.
100failThis vendor post is inactive.
101failThere was a problem inserting the lead into the system.
102failThere is already a lead with this phone number in the account.
103failThere is already a lead with this phone number in this vendor.
104failYou must provide at least one valid phone number or one valid email address.
105failThere is already a lead with this phone number in the system.
106failThere is already a lead with this phone number in the account based on criteria.
107failThere is already a lead with this phone number in this vendor based on date criteria.
108failThere is already a lead with this phone number in the system based on criteria.
110failThis vendor rejects leads from the provided State.
111failThis vendor does not accept leads from the provided State.
112failThis vendor rejects certain states and no State was provided.
113failThis vendor accepts certain states and no State was provided.
114failThere is already a lead with this email address in the account.
115failThere is already a lead with this email address in this vendor.
116failThere is already a lead with this email address in the system.
117failThere is already a lead with this email address in the account based on criteria.
118failThere is already a lead with this email address in this vendor based on date criteria.
119failThere is already a lead with this email address in the system based on criteria.
120failThere is already a lead with this data in the account.
121failThere is already a lead with this data in this vendor.
122failThere is already a lead with this data in the system.
123failThere is already a lead with this data in the account based on criteria.
124failThere is already a lead with this data in this vendor based on date criteria.
125failThere is already a lead with this data in the system based on criteria.
126failTried to find Dupe by Lead ID and Failed. Nothing was updated or attached.
127failThere is already a lead with this Lead ID in the system.
128failThis vendor rejects leads from the provided Zipcode.
129failThis vendor does not accept leads from the provided Zipcode.
130failThis vendor rejects certain zipcodes and no Zipcode was provided.
131failThis vendor accepts certain zipcodes and no Zipcode was provided.
132failThis vendor rejects leads from the provided Areacode.
133failThis vendor does not accept leads from the provided Areacode.
134failThis vendor rejects certain areacodes and no Phone Number was provided.
135failThis vendor accepts certain areacodes and no Phone Number was provided.
136failThis vendor accepts leads only at certain times and the current time is not in that range.
137failThis vendor rejects leads at certain times and the current time is in that range.
138failToo many leads have been sent for the hour.
139failToo many leads have been sent for the day.
140failToo many leads have been sent for the week.
141failToo many leads have been sent for the month.
142failTried to add lead as a dependent and failed Dependent Dupe check Criteria
200failPhone Numbers found in TLDialer DNC List
201failPhone Numbers found in Configured Filter Phone Groups
300failInsufficent data to certify lead. Phone, First, Last, City and State are required.
301failLead belong to a known Litigator.
302failLead has an invalid phone number.
303failLead belongs to a known Litigator or is a Bad Number.
304failLead has already been claimed.
305failDatabase problem, Please try again.
306failProcessing problem, please try again.
350failPhone number could not be validated.
351failPhone number is in the Blacklist.
352failPhone number is in the Suppression List.
353failPhone number's status could not be determined.
360failPhone number could not be validated by DNC.com
361failPhone Number is in the DNC.com Database
363failPhone Number's status could not be determined in DNC.com
400failProblem Reading XML Document

Primary Contact / Lead Fields

Primary fields have the most fields available and require no prefix.

name
  • Any String
    •
first_name
  • Any String
    •
middle_name
  • Any String
    •
last_name
  • Any String
    •
address
  • Any String
    •
address2
  • Any String
    •
city
  • Any String
    •
state
  • Any String
    •
zipcode
  • Any String
    •
county
  • Any String
    •
country
  • Any String
    •
email
  • Valid Email
    •
email2
  • Valid Email
    •
phone
  • 10 Digit Phone Number
    •
phone_type
  • System Field ID
    •
  • phone_type
phone_part1
  • Any String
    •
phone_part2
  • Any String
    •
phone_part3
  • Any String
    •
phone2
  • 10 Digit Phone Number
    •
phone2_type
  • System Field ID
    •
  • phone_type
phone3
  • 10 Digit Phone Number
    •
phone3_type
  • System Field ID
    •
  • phone_type
heightft
  • Any String
    •
heightin
  • Any String
    •
weight
  • Any String
    •
dob
  • Any String
    •
dob_yy
  • Any String
    •
dob_mm
  • Any String
    •
age
  • Any String
    •
ssn
  • Any String
    •
mothers_maiden_name
  • Any String
    •
drivers_license
  • Any String
    •
drivers_license_state
  • Any String
    •
time_zone
  • Any String
    •
pcp_name
  • Any String
    •
pcp_id
  • Any String
    •
pcp_office
  • Any String
    •
mrn
  • Any String
    •
empi
  • Any String
    •
medicare_claim_number
  • Any String
    •
medicare_part_a
  • Any String
    •
medicare_part_b
  • Any String
    •
medicaid_number
  • Any String
    •
medicaid_level
  • System Field ID
    •
  • medicaid_level
medicaid_username
  • Any String
    •
medicaid_password
  • Any String
    •
scope_of_appointment
  • Any String
    •
enrollment_eligibility
  • System Field ID
    •
  • enrollment_eligibility
conditions
  • Any String
    •
condition_diabetes
  • Boolean
    •
condition_cancer
  • Boolean
    •
condition_heart_disease
  • Boolean
    •
medications
  • Any String
    •
smoker
  • Boolean
    •
married
  • System Field ID
    •
  • marital_status
veteran
  • Boolean
    •
insured
  • Boolean
    •
occupation
  • Any String
    •
sob
  • Any String
    •
cob
  • Any String
    •
gender
  • Any String
    •
language
  • System Field ID
    •
  • language
contact_time
  • Any String
    •
insured_premium
  • Any String
    •
insured_carrier
  • System Field ID
    •
  • carrier
insured_intent
  • System Field ID
    •
  • insured_intent
budget
  • Any String
    •
annual_income
  • Any String
    •
requested_term
  • Any String
    •
requested_coverage
  • Any String
    •
tracking_id
  • Any String
    •
campaign_id
  • Any String
    •
reference_id
  • Any String
    •
ip_address
  • Any String
    •
referrer
  • Any String
    •
page
  • Any String
    •
image
  • Any String
    •
link
  • Any String
    •
newsletter
  • Any String
    •
marketing
  • Any String
    •
import_id
  • Any String
    •
import_source
  • Any String
    •
import_row
  • Any String
    •
creator_email
  • Any String
    •
modifier_email
  • Any String
    •
assigned_email
  • Any String
    •
agent_email
  • Any String
    •
fronter_email
  • Any String
    •
lmb_email
  • Any String
    •
status_id
  • System Field ID
    •
  • status
vendor_id
  • System Field ID
    •
  • vendor
cost
  • Any String
    •
callback
  • Any String
    •
callback_description
  • Any String
    •
callback_user_id
  • Any String
    •
callback_user_email
  • Any String
    •

Spouse Fields

Spouse fields act as dependent fields except they have the static prefix spouse_ and are automatically set as spouse.

spouse_first_name
  • Any String
    •
spouse_middle_name
  • Any String
    •
spouse_last_name
  • Any String
    •
spouse_email
  • Valid Email
    •
spouse_email2
  • Valid Email
    •
spouse_phone
  • 10 Digit Phone Number
    •
spouse_phone_type
  • System Field ID
    •
  • phone_type
spouse_phone2
  • 10 Digit Phone Number
    •
spouse_phone2_type
  • System Field ID
    •
  • phone_type
spouse_phone3
  • 10 Digit Phone Number
    •
spouse_phone3_type
  • System Field ID
    •
  • phone_type
spouse_occupation
  • Any String
    •
spouse_annual_income
  • Any String
    •
spouse_relationship
  • System Field ID
    •
  • relationship
spouse_heightft
  • Any String
    •
spouse_heightin
  • Any String
    •
spouse_weight
  • Any String
    •
spouse_dob
  • Any String
    •
spouse_gender
  • Any String
    •
spouse_language
  • System Field ID
    •
  • language
spouse_enrollment_eligibility
  • System Field ID
    •
  • enrollment_eligibility
spouse_exclude
  • Any String
    •
spouse_ssn
  • Any String
    •
spouse_mrn
  • Any String
    •
spouse_empi
  • Any String
    •
spouse_medicare_claim_number
  • Any String
    •
spouse_medicare_part_a
  • Any String
    •
spouse_medicare_part_b
  • Any String
    •
spouse_medicaid_number
  • Any String
    •
spouse_medicaid_level
  • System Field ID
    •
  • medicaid_level
spouse_medicaid_username
  • Any String
    •
spouse_medicaid_password
  • Any String
    •
spouse_student
  • Boolean
    •
spouse_smoker
  • Boolean
    •
spouse_medications
  • Any String
    •
spouse_conditions
  • Any String
    •
spouse_pcp_name
  • Any String
    •
spouse_pcp_id
  • Any String
    •
spouse_pcp_office
  • Any String
    •
spouse_import_id
  • Any String
    •
spouse_import_source
  • Any String
    •
spouse_import_row
  • Any String
    •

Dependent Fields

Replace x with the number of a dependents up to the maximum amount of dependents. For example, if we have childx_first_name and max dependents set to 3, we will be listening for child1_first_name, child2_first_name and child3_first_name. If you are posting relational data to the system, you must send over our internal ID number of the data points, not text. Relational fields include things like creator_id, etc. Please request access to the data mappings separately if needed.

Max Dependents: 5

dependentx_first_name
  • Any String
    •
dependentx_middle_name
  • Any String
    •
dependentx_last_name
  • Any String
    •
dependentx_email
  • Valid Email
    •
dependentx_email2
  • Valid Email
    •
dependentx_phone
  • 10 Digit Phone Number
    •
dependentx_phone_type
  • System Field ID
    •
  • phone_type
dependentx_phone2
  • 10 Digit Phone Number
    •
dependentx_phone2_type
  • System Field ID
    •
  • phone_type
dependentx_phone3
  • 10 Digit Phone Number
    •
dependentx_phone3_type
  • System Field ID
    •
  • phone_type
dependentx_occupation
  • Any String
    •
dependentx_annual_income
  • Any String
    •
dependentx_relationship
  • System Field ID
    •
  • relationship
dependentx_heightft
  • Any String
    •
dependentx_heightin
  • Any String
    •
dependentx_weight
  • Any String
    •
dependentx_dob
  • Any String
    •
dependentx_gender
  • Any String
    •
dependentx_language
  • System Field ID
    •
  • language
dependentx_enrollment_eligibility
  • System Field ID
    •
  • enrollment_eligibility
dependentx_exclude
  • Any String
    •
dependentx_ssn
  • Any String
    •
dependentx_mrn
  • Any String
    •
dependentx_empi
  • Any String
    •
dependentx_medicare_claim_number
  • Any String
    •
dependentx_medicare_part_a
  • Any String
    •
dependentx_medicare_part_b
  • Any String
    •
dependentx_medicaid_number
  • Any String
    •
dependentx_medicaid_level
  • System Field ID
    •
  • medicaid_level
dependentx_medicaid_username
  • Any String
    •
dependentx_medicaid_password
  • Any String
    •
dependentx_student
  • Boolean
    •
dependentx_smoker
  • Boolean
    •
dependentx_medications
  • Any String
    •
dependentx_conditions
  • Any String
    •
dependentx_pcp_name
  • Any String
    •
dependentx_pcp_id
  • Any String
    •
dependentx_pcp_office
  • Any String
    •
dependentx_import_id
  • Any String
    •
dependentx_import_source
  • Any String
    •
dependentx_import_row
  • Any String
    •

Policy Fields

Replace x with the number of a policies up to the maximum amount of policies. For example, if we have policyx_premium and max policies set to 3, we will be listening for policy1_premium, policy2_premium and policy3_premium. If you are posting relational data to the system, you must send over our internal ID number of the data points, not text. Relational fields include things like creator_id, etc. Please request access to the data mappings separately if needed.

Max Policies: 5

policyx_application_number
  • Any String
    •
policyx_policy_number
  • Any String
    •
policyx_policy_name
  • Any String
    •
policyx_member_id
  • Any String
    •
policyx_duration
  • System Field ID
    •
  • duration
policyx_premium
  • Any String
    •
policyx_premium_subsidized
  • Any String
    •
policyx_deposit
  • Any String
    •
policyx_enrollment_fee
  • Any String
    •
policyx_admin_fee
  • Any String
    •
policyx_deductible
  • Any String
    •
policyx_coinsurance
  • Any String
    •
policyx_rider_id
  • System Field ID
    •
  • rider_id
policyx_paid_up_id
  • System Field ID
    •
  • paid_up
policyx_issue_type_id
  • System Field ID
    •
  • issue_type
policyx_issue_test_id
  • System Field ID
    •
  • issue_test
policyx_rating_class_id
  • System Field ID
    •
  • rating_class
policyx_dividend_option_id
  • System Field ID
    •
  • dividend_option
policyx_coverage_type_id
  • System Field ID
    •
  • coverage_type
policyx_nfo_id
  • System Field ID
    •
  • nfo
policyx_mec_id
  • System Field ID
    •
  • mec
policyx_moop
  • Any String
    •
policyx_moop_coverage
  • Any String
    •
policyx_enrollment_eligibility
  • System Field ID
    •
  • enrollment_eligibility
policyx_marketplace
  • Any String
    •
policyx_marketplace_id
  • Any String
    •
policyx_beneficiary_name
  • Any String
    •
policyx_beneficiary_dob
  • Date Time
    •
policyx_beneficiary_relationship
  • System Field ID
    •
  • relationship
policyx_contingent_name
  • Any String
    •
policyx_contingent_dob
  • Date Time
    •
policyx_contingent_relationship
  • System Field ID
    •
  • relationship
policyx_face_amount
  • Any String
    •
policyx_terms
  • Any String
    •
policyx_term_current
  • Any String
    •
policyx_billing_cycle_id
  • System Field ID
    •
  • billing_cycle
policyx_payment_type
  • System Field ID
    •
  • payment_type
policyx_aor_change
  • Boolean
    •
policyx_rewrite
  • Any String
    •
policyx_rewrite_refused
  • Any String
    •
policyx_paid
  • Any String
    •
policyx_date_effective
  • Date Time
    •
policyx_date_terminate
  • Date Time
    •
policyx_date_posted
  • Date Time
    •
policyx_date_issued
  • Date Time
    •
policyx_date_drafted
  • Date Time
    •
policyx_date_inforce
  • Date Time
    •
policyx_date_paid
  • Date Time
    •
policyx_commission_paid
  • Any String
    •
policyx_commission_paid_chargeback
  • Any String
    •
policyx_commission_received
  • Any String
    •
policyx_commission_received_chargeback
  • Any String
    •
policyx_billing_first_name
  • Any String
    •
policyx_billing_last_name
  • Any String
    •
policyx_billing_address
  • Any String
    •
policyx_billing_city
  • Any String
    •
policyx_billing_state
  • Any String
    •
policyx_billing_zipcode
  • Any String
    •
policyx_bank_name
  • Any String
    •
policyx_bank_account_number
  • Any String
    •
policyx_bank_routing_number
  • Any String
    •
policyx_bank_name_on_account
  • Any String
    •
policyx_bank_account_type
  • Any String
    •
policyx_cc_number
  • Any String
    •
policyx_cc_cvv
  • Any String
    •
policyx_cc_exp_mm
  • Any String
    •
policyx_cc_exp_yy
  • Any String
    •
policyx_cc_type
  • System Field ID
    •
  • cc_type
policyx_import_id
  • Any String
    •
policyx_import_source
  • Any String
    •
policyx_import_row
  • Any String
    •
policyx_creator_id
  • System Field ID
    •
  • user
policyx_lmb
  • System Field ID
    •
  • user
policyx_agent_id
  • System Field ID
    •
  • user
policyx_agent_of_record
  • System Field ID
    •
  • user
policyx_verifier_id
  • System Field ID
    •
  • user
policyx_submitter_id
  • System Field ID
    •
  • user
policyx_kicker_id
  • System Field ID
    •
  • user
policyx_interrupter_id
  • System Field ID
    •
  • user
policyx_canceller_id
  • System Field ID
    •
  • user
policyx_status_id
  • System Field ID
    •
  • policy_status
policyx_carrier_id
  • System Field ID
    •
  • carrier
policyx_product_id
  • System Field ID
    •
  • product_customized
policyx_group_id
  • System Field ID
    •
  • group
policyx_rewrite_id
  • Any String
    •
policyx_primary_id
  • Any String
    •
policyx_date_created
  • Any String
    •
policyx_date_modified
  • Any String
    •
policyx_date_converted
  • Any String
    •
policyx_date_verified
  • Date Time
    •
policyx_date_sold
  • Date Time
    •
policyx_date_kicked
  • Date Time
    •
policyx_date_interrupted
  • Any String
    •
policyx_date_reactivated
  • Any String
    •
policyx_date_cancelled
  • Date Time
    •

Note Fields

Replace x with the number of a notes up to the maximum amount of notes. For example, if we have notex_note and max notes set to 3, we will be listening for note1_note, note2_note and note3_note. If you are posting relational data to the system, you must send over our internal ID number of the data points, not text. Relational fields include things like creator_id, etc. Please request access to the data mappings separately if needed.

Max Notes: 5

notex_note
  • Any String
    •
notex_csr
  • Boolean
    •
notex_csr_agent_id
  • System Field ID
    •
  • user
notex_csr_requester_id
  • System Field ID
    •
  • user
notex_csr_completer_id
  • System Field ID
    •
  • user
notex_csr_date_scheduled
  • Date Time
    •
notex_csr_date_requested
  • Date Time
    •
notex_csr_date_completed
  • Date Time
    •
notex_import_id
  • Any String
    •
notex_import_source
  • Any String
    •
notex_import_row
  • Any String
    •
notex_user_id
  • System Field ID
    •
  • user
notex_lmb
  • Any String
    •
notex_date_created
  • Date Time
    •
notex_date_modified
  • Date Time
    •