Child pages
  • Data Affiliates V4.0 API Partner Specification

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

Back To Contents

Date

Rev.

Comments

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="7f6c265f-227e-4ebb-a13b-b07f06dc5ce0"><ac:plain-text-body><![CDATA[

3/21/2011

4.0

New version of document specific to V4.0 API, based on [ original V3.0 API document [JDR]

http: 4/07/extranet.allwebleads.com/display/ENG/Partner+Specification+Portal#PartnerSpecificationPortal-Version3.0API] 2011

4.1

Updated staging test application information. Added clarification that the actual web service endpoints do not support HTTPS GET protocol. [JDR]

]]></ac:plain-text-body></ac:structured-macro>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="a4685ee0-5887-496b-9b2e-940d7b45092c"><ac:plain-text-body><![CDATA[

4/07 4/13/2011

4.2

Updated for new Health Insurance and Home Insurance support, as well as Undersold support [JDR]

4/25/2011

4.1 Updated staging test application information. Added clarification that the actual web service endpoints do not support HTTPS GET protocol. 3

Moved document to the AWL extranet wiki [JDR]

5/02/2011

4.4

Fixed incorrect documentation for Price Presentation staging and production URLs [JDR]

]]></ac:plain-text-body></ac:structured-macro>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="2ae0fc73-4af5-4717-8167-4681d3399d96"><ac:plain-text-body><![CDATA[

4/13 5/12/2011

4.5

Updated "Staging Environment Test Application" section to remove note about lead service URL not being defaulted, as it now is. [JDR]

5/17/2011

4.2 6

Updated for new Health Insurance and Home Insurance support, as well as Undersold support spec with latest insurance provider carriers, split list between Undersold supported and current insurance supported carriers. [JDR]

]]></ac:plain-text-body></ac:structured-macro>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="99b9b34e-83db-4362-9ef1-06af47df509f"><ac:plain-text-body><![CDATA[

4/25 7/26/2011

4.7

Updated spec and schemas to include new Leg Ping and Post Lead APIs.

10/6/2011

4.3

Moved document to the AWL extranet wiki [JDR]

]]></ac:plain-text-body></ac:structured-macro>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="ca878c32-6603-42bd-8632-5b2a87ffde1e"><ac:plain-text-body><![CDATA[

5/02/2011

4.4

Fixed incorrect documentation for Price Presentation staging and production URLs [JDR]

]]></ac:plain-text-body></ac:structured-macro>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="eeaa8629-a692-4d3f-b9a1-de8ef3c9bf42"><ac:plain-text-body><![CDATA[

5/12/2011

4.5

Updated "Staging Environment Test Application" section to remove note about lead service URL not being defaulted, as it now is. [JDR]

]]></ac:plain-text-body></ac:structured-macro>

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="17f2f83a-292c-44ac-97ab-8ea09a3eb010"><ac:plain-text-body><![CDATA[

5/17/2011

4.6

Updated spec with latest insurance provider carriers, split list between Undersold supported and current insurance supported carriers. [JDR]

]]></ac:plain-text-body></ac:structured-macro>

7/26/2011

4.7

Updated spec and schemas to include new Leg Ping and Post Lead APIs.

10/6/2011

4.8

Updated features section to include information about the Lead Source Id parameter.

3/5/2012

4.9

Updated spec/schema to add support for LeadIdToken parameter.

4/23/2012

4.10

Updated schema and added description for "NotSoldExclude" distribution directives.

8/2/2012

4.11

Added AWL/LeadiD Getting Started Guide information to enhance LeadIdToken parameter information.

7/15/2013

4.12

Added LeadMetaData node to the schema which has the following elements in it: IpAddress, LeadBornOnDateTimeUtc, and UserAgent.

8/1/2013

4.13

Updated the Insurance Carrier lists.

8/5/2013

4.14

Schema was updated to add new optional parameters. Parameters include: marital status for health, home, renters, and life lead types, gender for home and renters lead types, first name and last name for health lead dependents, and "is military" indicator for health lead type.

3/13/2014

4.15

Lead samples were added under the Lead Types section.

5/27/2014

4.16

Added full list of possible API ping/post responses.

8/26/2014

4.17

Added optional "Motorcycle" element to Vehicle node in AutoInsuranceRequest.

11/12/2014

4.18

Added sample raw ping/post request/responses for Auto and Health leads.

1/22/2015

4.19

Updated lead schema. Removed duplicate Marital element in Health, LTC, and Disability types. Added QualifyingLifeEvent element in Health type.

11/24/2015

4.20

Updated the Current Provider Carrier List in order to remove carrier strings containing ampersands. The ampersands have been changed to "and" instead.

4/25/2016

4.21

Updated the Undersold Carrier List and added several new carriers

5/11/2017

4.22

Added support for Inbound Warm Transfer Call Affiliates. Updated LeadXMLSchema.xsd and PricePresentationResult.xsd.

Introduction

Back To Contents

This document details the information necessary for Data Affiliate partners to begin selling leads to All Web Leads, Inc. (referred to hereafter as AWL) via the AWL Version 4.0 Data Affiliate web service API.

Data Affiliates are defined as those business partners that offer complete Lead Data for purchase to AWL by means of a real time web service provided by AWL.

The AWL Version 4.0 API replaces the previous Version 3.0 API. All partners are encouraged to integrate with the Version 4.0 API, as the 3.0 API will slowly be phased out and discontinued early in 2012.

The Version 4.0 API is intended to be an evolutionary step from the non-SOAP capabilities of the 3.0 API. The primary difference between the V4.0 API and the V3.0 API is that the SOAP-based web services are no longer support, and the V4.0 API relies on entirely new Lead definitions (new lead XML Schema, included along with this specification document).

Supporting XML Schema Files

Back To Contents

Supported Features

Back To Contents

Lead Types

Back To Contents

Currently, the Version 4.0 API only supports the following insurance lead types:

(Click the link to see a sample lead for the given lead type)

Lead Subtypes

Back To Contents

In addition to the above lead types, a more detailed categorization, or "Lead Subtype", is also supported. Lead Subtypes are commonly used to define payout and daily lead limit information associated with each Data Affiliate account. Note that not all Lead Types have associated Lead Subtypes. Lead Subtypes are not explicitly represented in the AWL Lead XML Schema, but are instead evaluated at runtime as business rules.

Auto

Back To Contents

...

8

Updated features section to include information about the Lead Source Id parameter.

3/5/2012

4.9

Updated spec/schema to add support for LeadIdToken parameter.

4/23/2012

4.10

Updated schema and added description for "NotSoldExclude" distribution directives.

8/2/2012

4.11

Added AWL/LeadiD Getting Started Guide information to enhance LeadIdToken parameter information.

7/15/2013

4.12

Added LeadMetaData node to the schema which has the following elements in it: IpAddress, LeadBornOnDateTimeUtc, and UserAgent.

8/1/2013

4.13

Updated the Insurance Carrier lists.

8/5/2013

4.14

Schema was updated to add new optional parameters. Parameters include: marital status for health, home, renters, and life lead types, gender for home and renters lead types, first name and last name for health lead dependents, and "is military" indicator for health lead type.

3/13/2014

4.15

Lead samples were added under the Lead Types section.

5/27/2014

4.16

Added full list of possible API ping/post responses.

8/26/2014

4.17

Added optional "Motorcycle" element to Vehicle node in AutoInsuranceRequest.

11/12/2014

4.18

Added sample raw ping/post request/responses for Auto and Health leads.

1/22/2015

4.19

Updated lead schema. Removed duplicate Marital element in Health, LTC, and Disability types. Added QualifyingLifeEvent element in Health type.

11/24/2015

4.20

Updated the Current Provider Carrier List in order to remove carrier strings containing ampersands. The ampersands have been changed to "and" instead.

4/25/2016

4.21

Updated the Undersold Carrier List and added several new carriers

5/11/2017

4.22

Added support for Inbound Warm Transfer Call Affiliates. Updated LeadXMLSchema.xsd and PricePresentationResult.xsd.

1/31/2018

4.23

Added language about omitting the ContactInfo node in the ping XML and omitting the ProductionEnvironment element from ping and post XML.

2/22/2018

4.24

Updated LeadXMLSchema.xsd

3/29/2019

4.25

Added Nonbinary gender option to GenderType.

9/26/2019

4.26

Updated documentation about the usage of the ProductionEnvironment flag.

Introduction

Back To Contents

This document details the information necessary for Data Affiliate partners to begin selling leads to All Web Leads, Inc. (referred to hereafter as AWL) via the AWL Version 4.0 Data Affiliate web service API.

Data Affiliates are defined as those business partners that offer complete Lead Data for purchase to AWL by means of a real time web service provided by AWL.

The AWL Version 4.0 API replaces the previous Version 3.0 API. All partners are encouraged to integrate with the Version 4.0 API, as the 3.0 API will slowly be phased out and discontinued early in 2012.

The Version 4.0 API is intended to be an evolutionary step from the non-SOAP capabilities of the 3.0 API. The primary difference between the V4.0 API and the V3.0 API is that the SOAP-based web services are no longer support, and the V4.0 API relies on entirely new Lead definitions (new lead XML Schema, included along with this specification document).

Supporting XML Schema Files

Back To Contents

Supported Features

Back To Contents

Lead Types

Back To Contents

Currently, the Version 4.0 API only supports the following insurance lead types:

(Click the link to see a sample lead for the given lead type)

Lead Subtypes

Back To Contents

In addition to the above lead types, a more detailed categorization, or "Lead Subtype", is also supported. Lead Subtypes are commonly used to define payout and daily lead limit information associated with each Data Affiliate account. Note that not all Lead Types have associated Lead Subtypes. Lead Subtypes are not explicitly represented in the AWL Lead XML Schema, but are instead evaluated at runtime as business rules.

Auto

Back To Contents

  • Premium Auto
    • Require 1 Driver 22 or Older
    • Require all drivers currently insured
    • Require all drivers have valid licenses /no license suspension (meaning ACTIVE and TEMPORARY is OK)
    • Require NO SR-22
    • Require NO DUI/DWI
    • Require One or Less Tickets
    • Require NO Major Violations (meaning no DUI, and no careless driving)
    • Require No At Fault Accidents
      • Note that if the user selects that an accident is not at-fault, but then selects "Your Vehicle Hit Other Vehicle", we treat that accident as an at-fault accident
  • Standard Auto
    • Require 1 Driver 18 or Older
    • Require all drivers currently insured
    • Require all drivers have valid licenses/no license suspension (meaning ACTIVE and TEMPORARY is OK)
    • Require NO SR-22
    • Require NO DUI/DWI
    • Require One Three or Less Tickets
    • Require NO Major Violations (meaning no DUI, and no careless driving)
    • Require No At Fault Accidents
      • Note that if the user selects that an accident is not at-fault, but then selects "Your Vehicle Hit Other Vehicle", we treat that accident as an at-fault accident
  • Standard Auto
    • Require 1 Driver 18 or Older
    • Require all drivers currently insured
    • Require all drivers have valid licenses/no license suspension
    • Require NO SR-22
    • Require NO DUI/DWI
    • Require Three or Less Tickets
    • Require One or Less At Fault Accidents
    • One or Less At Fault Accidents
  • Substandard Auto
    • Require 1 Driver 18 or Older
    • Anything not meeting Premium or Standard risk
  • Juvenile Auto
    • All drivers under age 18

...

Code Block
<AffiliateInfo>
    <Username>User</Username>
    <Password>Pass</Password>
    <TrackingCampaign>MyCampaign</TrackingCampaign>
    <LeadSourceID>12345</LeadSourceID>
    <ProductionEnvironment>true</ProductionEnvironment>
</AffiliateInfo>

See Lead Format Schema for more details.

LeadId Token

Back To Contents

We support an optional parameter called require that the "LeadIdToken" be included in the Lead XML. This parameter is a string type of maximum length 36. This is a token created by LeadId.com (Jornaya) for lead validation purposes.

For more information, please refer to our LeadiD/All Web Leads Getting Started Guide

...

Code Block
<AffiliateInfo>
    <Username>User</Username>
    <Password>Pass</Password>
    <TrackingCampaign>MyCampaign</TrackingCampaign>
    <LeadSourceID>12345</LeadSourceID>
    <LeadIdToken>PassedToken</LeadIdToken>
</AffiliateInfo>
   <ProductionEnvironment>true</ProductionEnvironment>

TrustedForm Token

Back To Contents

We support an optional parameter called "TrustedFormToken". This parameter is a string of maximum length 40. This is a token created by Active Prospect for validation purposes.

Sample AffiliateInfo xml snippet:

Code Block
<AffiliateInfo>
    <Username>User</Username>
    <Password>Pass</Password>
    <TrackingCampaign>MyCampaign</TrackingCampaign>
    <LeadSourceID>12345</LeadSourceID>
    <TrustedFormToken>PassedToken</TrustedFormToken>
</AffiliateInfo>

LeadMetaData

We support a few optional fields under the optional "LeadMetaData" node. These fields are defined below:

...

  • XmlString (String)
    • An XML string containing the lead object. The XML string must conform to the AWL Lead XML V1.5 Schema (included with this documentation)
    • XML string must be in UTF-8 format and must NOT include a Unicode byte order mark (BOM)
    • The ContactInfo node should be omitted in the ping XML

Example HTTP POST Data Payload

...

  • LeadID (String)
    • A string containing the "LeadID" value returned by a previous successful call to the "Price Presentation Ping Lead" API that uniquely identifies the ping session and is used to associate this API call with the price bid returned by the ping
  • XmlString (String)
    • An XML string containing the lead object. The XML string must conform to the AWL Lead XML V1.5 Schema (included with this documentation)
    • XML string must be in UTF-8 format and must NOT include a Unicode byte order mark (BOM)
    • XML With the exception of the ContactInfo node and the FirstName/LastName elements (Auto leads only), the XML string must be equivalent to XML provided in previous successful call to the "Price Presentation Ping Lead" API

...

  • Result
    • Values:
      • "OK"
        • Indicates that the request was successfully processed
        • Only indicates that the lead was bid upon in the event that a non-zero "Payout" and a valid "LeadID" value is returned
      • "ERROR"
        • Indicates that an error occurred during processing
  • ErrorType
    • Provided when the "Result" is "ERROR" to provide additional information
    • Values:
      • "XML Validation"
      • "Data Validation"
      • "Login"
      • "Duplicate"
      • "Internal Server Error"
  • ErrorDescription
    • Provided when the "Result" is "ERROR" to provide additional information
    • Values consist of a descriptive human-readable string. A few examples:
      • "Invalid Username/Password"
      • "XML Parse/Validation Failure"
      • "Re-post of identical lead from same partner"
      • "Unknown error occurred processing lead"
      • Etc.
  • Payout
    • Provided when the "Result" is "OK", and the AWL system has successfully placed a bid on the incoming warm transfer
    • Represents the expected/estimated payout associated with a potential subsequent post of the same warm transfer
  • LeadID
    • Provided when the "Result" is "OK", and the "Payout" is greater than $0.00
    • The Lead ID value is not a "real" warm transfer identifier within the AWL system, but instead is actually a ping session identifier that must be used in a subsequent "Price Presentation Post Inbound Warm Transfer" API call if the partner chooses to offer the full warm transfer data to AWL for sale at the bid-upon price point
    • This value should be logged/recorded in each partner's system
  • DataFieldValidation
    • Provided when the "Result" is "ERROR". Zero or more "DataFieldValidation" nodes may be included indicate which field or fields triggered an error response.
    • DataField
      • Identifies the data field (element) within the Lead XML that triggered a validation error
      • Values:
        • nameFirst
        • nameLast
        • nameMiddle
        • namePrefix
        • nameSuffix
        • addressStreet
        • addressStreet2
        • city
        • state
        • zipCode
        • phoneDay
        • phoneEvening
        • email
        • currentlyInsured
        • insuranceProvider
        • lengthOfCoverage
        • coverageExpiration
    • DataFieldErrorType
      • Identifies the type of validation error that occurred
      • Values:
        • Fail
        • Warning
    • DataFieldErrorMessage
      • Provides additional information related to the validation error that occurred
      • May be empty when no additional information is available
  • AllowTransfer
    • Boolean field that indicates whether or not the warm transfer has been accepted.

Price Presentation Post Inbound Warm Transfer API

...

  • LeadID (String)
    • A string containing the "LeadID" value returned by a previous successful call to the "Price Presentation Ping Inbound Warm Transfer" API that uniquely identifies the ping session and is used to associate this API call with the price bid returned by the ping
  • XmlString (String)
    • An XML string containing the lead object. The XML string must conform to the AWL Lead XML V1.5 Schema (included with this documentation)
    • XML string must be in UTF-8 format and must NOT include a Unicode byte order mark (BOM)
    • XML string must be equivalent to With the exception of the ContactInfo node and the FirstName/LastName elements (Auto leads only), the XML string must be equivalent to XML provided in previous successful call to the "Price Presentation Ping Inbound Warm Transfer" API

...

  • XmlString (String)
    • An XML string containing the lead object. The XML string must conform to the AWL Lead XML V1.5 Schema (included with this documentation)
    • XML string must be in UTF-8 format and must NOT include a Unicode byte order mark (BOM)
    • The ContactInfo node should be omitted in the ping XML

Relevant schemas:

Lead Format Schema
API Response Schema

...

  • LeadID (String)
    • A string containing the "LeadID" value returned by a previous successful call to the "Legs Ping Lead" API that uniquely identifies the ping session and is used to associate this API call with the leg price bids returned by the ping
  • XmlString (String)
    • An XML string containing the lead object. The XML string must conform to the AWL Lead XML V1.5 Schema (included with this documentation)
    • XML string must be in UTF-8 format and must NOT include a Unicode byte order mark (BOM)
    • With the exception of the ContactInfo node and the FirstName/LastName elements (Auto leads only), the XML string must be equivalent to XML provided in previous successful call to the "Legs Ping Lead" API.

Relevant schemas:

Lead Format Schema
API Response Schema

...

Price Presentation Legs Post API:
https://ws.allwebleads.com/leads/4.0/LeadServiceHttpPost.svc/LegsPostLead

...

Production Environment Flag

Back To Contents

In general, all testing should be conducted within the AWL dedicated staging environment. On the other hand, certain classes or problems present themselves that require partners to send a very limited number of test leads into the AWL production system.

Unfortunately, it is not possible to send a test lead into the AWL production environment and receive a successful response.

It is possible to send a test lead into the production environment, which will result in a special error result that indicates that the operation would have had a high likelihood of succeeding.

To send a test lead into the AWL production environment, simply set the "ProductionEnvironment" flag in the lead XML to "true". After integration testing is complete and is ready to go live, the"ProductionEnvironment" flag should always be set to "true" or the lead will not be counted as a live lead.

The ProductionEnvironment flag can be found within the XML here:

InsuranceRequest/AffliateInfo/ProductionEnvironment

If a test lead is not sent properly, it will be treated as a real lead. Please use extreme caution and care when submitting test leads into the AWL production environment.

Note, that duplicate detection rules continue to apply within the production environment even with regard to test leads. This means that each production-targeted test lead must have a unique email address, daytime phone number, and street address whenever contact information is provided.

\

All testing should be conducted within the AWL dedicated staging environment. The ProductionEnvironment flag should be completely omitted from the Lead XML in both the staging and production.

Quick Start Guide

If you would like to see a summarized version to get started, please check out the Quick Start Guide.

...

Code Block
POST https://dastaging-lm.dev.allwebleads.com/leads/4.0/LeadServiceHttpPost.svc/PricePresentationPingLead HTTP/1.1
Content-Type: application/x-www-form-urlencoded
User-Agent: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.1)
Host: dastaging-lm.dev.allwebleads.com
Content-Length: 3497
Expect: 100-continue

XmlString=<?xml version="1.0" encoding="utf-8"?><InsuranceRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><AffiliateInfo><Username>12696</Username><Password>MyPassword</Password><TrackingCampaign>MyTrackingCampaign</TrackingCampaign><LeadSourceID>SourceID</LeadSourceID><LeadIdToken>8731d15b-793c-4ea0-b7e2-35b35a66f063</LeadIdToken><ProductionEnvironment>true</ProductionEnvironment><LeadIdToken></AffiliateInfo><IsMobile>false</IsMobile><LeadMetaData><LeadBornOnDateTimeUtc>2014-11-11T03:31:21Z</LeadBornOnDateTimeUtc><IpAddress>204.205.123.125</IpAddress><UserAgent>UserAgentTextGoesHere</UserAgent></LeadMetaData><ZipCode>34747</ZipCode><AutoInsurance><Vehicles><Vehicle><Id>1</Id><Vin>*****************</Vin><Year>2008</Year><Make>VOLVO</Make><Model>S60 2.5T AWD</Model><SubModel>_</SubModel><Owner>Leased</Owner><Garage>No Cover</Garage><PrimaryUse>Commute Work</PrimaryUse><OneWay>90</OneWay><AnnualMileage>3000</AnnualMileage><Salvaged>true</Salvaged><Comprehensive>No Coverage</Comprehensive><Collision>50</Collision><Motorcycle>false</Motorcycle></Vehicle><Vehicle><Id>2</Id><Vin>*****************</Vin><Year>2008</Year><Make>VOLVO</Make><Model>S60 2.5T AWD</Model><SubModel>_</SubModel><Owner>Owned</Owner><Garage>No Cover</Garage><PrimaryUse>Business</PrimaryUse><OneWay>29</OneWay><AnnualMileage>5001</AnnualMileage><Salvaged>true</Salvaged><Comprehensive>250</Comprehensive><Collision>500</Collision><Motorcycle>false</Motorcycle></Vehicle></Vehicles><Drivers><Driver><Id>1</Id><FirstName>Scarlett</FirstName><LastName>Johnson</LastName><Gender>Male</Gender><Marital>Separated</Marital><DOB>1953-07-15</DOB><Relation>Self</Relation><DLicenseState>TX</DLicenseState><DLicenseStatus>Active</DLicenseStatus><LicensedAge>18</LicensedAge><VehicleId>1</VehicleId><Filing>false</Filing><Education>High School Diploma</Education><Occupation>Pharmaceutical/Biotech</Occupation><GoodStudent>true</GoodStudent><Suspension>false</Suspension></Driver><Driver><Id>2</Id><FirstName>Grace</FirstName><LastName>Johnson</LastName><Gender>Male</Gender><Marital>Single</Marital><DOB>1943-11-24</DOB><Relation>Parent</Relation><DLicenseState>TX</DLicenseState><DLicenseStatus>Active</DLicenseStatus><LicensedAge>17</LicensedAge><VehicleId>1</VehicleId><Filing>false</Filing><Education>Other</Education><Occupation>Advertising/Public Relations</Occupation><GoodStudent>false</GoodStudent><Suspension>false</Suspension></Driver></Drivers><Incidents><Ticket><DriverId>1</DriverId><Date>2012-07-01</Date><Description>Speeding</Description></Ticket><Ticket><DriverId>2</DriverId><Date>2011-11-01</Date><Description>Speeding</Description></Ticket><Ticket><DriverId>1</DriverId><Date>2011-12-01</Date><Description>Other Ticket</Description></Ticket><MajorViolation><DriverId>2</DriverId><Date>2012-03-01</Date><Description>Drunk Driving - no Injury</Description></MajorViolation><Accident><DriverId>2</DriverId><Date>2011-11-01</Date><Description>Chargeable Accident - Injury</Description><PaidAmount>63677</PaidAmount></Accident><Claim><DriverId>1</DriverId><Date>2013-07-01</Date><Description>Fire Hail Water Damage</Description><PaidAmount>25125</PaidAmount></Claim></Incidents><ApplicantInfo><Credit>Good</Credit><Residence>Own</Residence></ApplicantInfo><CurrentInsurance><CurrentlyInsured>false</CurrentlyInsured><CoverageType>Standard</CoverageType></CurrentInsurance><RequestedCoverage>Standard</RequestedCoverage></AutoInsurance></InsuranceRequest>

...

Code Block
POST https://dastaging-lm.dev.allwebleads.com/leads/4.0/LeadServiceHttpPost.svc/PricePresentationPostLead HTTP/1.1
Content-Type: application/x-www-form-urlencoded
User-Agent: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.1)
Host: dastaging-lm.dev.allwebleads.com
Content-Length: 3878
Expect: 100-continue

LeadID=677739597&XmlString=<?xml version="1.0" encoding="utf-8"?><InsuranceRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><AffiliateInfo><Username>12696</Username><Password>MyPassword</Password><TrackingCampaign>MyTrackingCampaign</TrackingCampaign><LeadSourceID>SourceID</LeadSourceID><LeadIdToken>8731d15b-793c-4ea0-b7e2-35b35a66f063</LeadIdToken><ProductionEnvironment>true</ProductionEnvironment><LeadIdToken></AffiliateInfo><IsMobile>false</IsMobile><LeadMetaData><LeadBornOnDateTimeUtc>2014-11-11T03:31:21Z</LeadBornOnDateTimeUtc><IpAddress>204.205.123.125</IpAddress><UserAgent>UserAgentTextGoesHere</UserAgent></LeadMetaData><ZipCode>34747</ZipCode><ContactInfo><FirstName>Roger</FirstName><LastName>Garcia</LastName><Address>42078 Main St</Address><ZipCode>34747</ZipCode><City>KISSIMMEE</City><County>Osceola</County><State>FL</State><PhoneDay>2547458235</PhoneDay><PhoneEve>2546493044</PhoneEve><PhoneCell>2547458235</PhoneCell><Email>RogerGarcia1528621581@test.org</Email><Comment>None</Comment></ContactInfo><AutoInsurance><Vehicles><Vehicle><Id>1</Id><Vin>*****************</Vin><Year>2008</Year><Make>VOLVO</Make><Model>S60 2.5T AWD</Model><SubModel>_</SubModel><Owner>Leased</Owner><Garage>No Cover</Garage><PrimaryUse>Commute Work</PrimaryUse><OneWay>90</OneWay><AnnualMileage>3000</AnnualMileage><Salvaged>true</Salvaged><Comprehensive>No Coverage</Comprehensive><Collision>50</Collision><Motorcycle>false</Motorcycle></Vehicle><Vehicle><Id>2</Id><Vin>*****************</Vin><Year>2008</Year><Make>VOLVO</Make><Model>S60 2.5T AWD</Model><SubModel>_</SubModel><Owner>Owned</Owner><Garage>No Cover</Garage><PrimaryUse>Business</PrimaryUse><OneWay>29</OneWay><AnnualMileage>5001</AnnualMileage><Salvaged>true</Salvaged><Comprehensive>250</Comprehensive><Collision>500</Collision><Motorcycle>false</Motorcycle></Vehicle></Vehicles><Drivers><Driver><Id>1</Id><FirstName>Scarlett</FirstName><LastName>Johnson</LastName><Gender>Male</Gender><Marital>Separated</Marital><DOB>1953-07-15</DOB><Relation>Self</Relation><DLicenseState>TX</DLicenseState><DLicenseStatus>Active</DLicenseStatus><LicensedAge>18</LicensedAge><VehicleId>1</VehicleId><Filing>false</Filing><Education>High School Diploma</Education><Occupation>Pharmaceutical/Biotech</Occupation><GoodStudent>true</GoodStudent><Suspension>false</Suspension></Driver><Driver><Id>2</Id><FirstName>Grace</FirstName><LastName>Johnson</LastName><Gender>Male</Gender><Marital>Single</Marital><DOB>1943-11-24</DOB><Relation>Parent</Relation><DLicenseState>TX</DLicenseState><DLicenseStatus>Active</DLicenseStatus><LicensedAge>17</LicensedAge><VehicleId>1</VehicleId><Filing>false</Filing><Education>Other</Education><Occupation>Advertising/Public Relations</Occupation><GoodStudent>false</GoodStudent><Suspension>false</Suspension></Driver></Drivers><Incidents><Ticket><DriverId>1</DriverId><Date>2012-07-01</Date><Description>Speeding</Description></Ticket><Ticket><DriverId>2</DriverId><Date>2011-11-01</Date><Description>Speeding</Description></Ticket><Ticket><DriverId>1</DriverId><Date>2011-12-01</Date><Description>Other Ticket</Description></Ticket><MajorViolation><DriverId>2</DriverId><Date>2012-03-01</Date><Description>Drunk Driving - no Injury</Description></MajorViolation><Accident><DriverId>2</DriverId><Date>2011-11-01</Date><Description>Chargeable Accident - Injury</Description><PaidAmount>63677</PaidAmount></Accident><Claim><DriverId>1</DriverId><Date>2013-07-01</Date><Description>Fire Hail Water Damage</Description><PaidAmount>25125</PaidAmount></Claim></Incidents><ApplicantInfo><Credit>Good</Credit><Residence>Own</Residence></ApplicantInfo><CurrentInsurance><CurrentlyInsured>false</CurrentlyInsured><CoverageType>Standard</CoverageType></CurrentInsurance><RequestedCoverage>Standard</RequestedCoverage></AutoInsurance></InsuranceRequest>

...

Code Block
POST https://dastaging-lm.dev.allwebleads.com/leads/4.0/LeadServiceHttpPost.svc/PricePresentationPingLead HTTP/1.1
Content-Type: application/x-www-form-urlencoded
User-Agent: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.1)
Host: dastaging-lm.dev.allwebleads.com
Content-Length: 2732
Expect: 100-continue
Connection: Keep-Alive

XmlString=<?xml version="1.0" encoding="utf-8"?><InsuranceRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><AffiliateInfo><Username>12696</Username><Password>MyPassword</Password><TrackingCampaign>MyTrackingCampaign</TrackingCampaign><LeadSourceID>SourceID</LeadSourceID><ProductionEnvironment>true</ProductionEnvironment><LeadSourceID></AffiliateInfo><LeadMetaData><LeadBornOnDateTimeUtc>2014-11-11T03:31:21Z</LeadBornOnDateTimeUtc><IpAddress>204.205.123.125</IpAddress><UserAgent>UserAgentTextGoesHere</UserAgent></LeadMetaData><ZipCode>87194</ZipCode><HealthInsurance><ApplicantInfo><FirstName>Uriel</FirstName><LastName>Jones</LastName><DOB>1951-02-20</DOB><Gender>Male</Gender><Marital>Married</Marital><Height_FT>6</Height_FT><Height_IN>3</Height_IN><Weight>200</Weight><Tobacco>false</Tobacco><Marital>Married</Marital><Occupation>Other</Occupation><USResidence>true</USResidence><HouseholdSize>7</HouseholdSize><Income>418945878</Income></ApplicantInfo><Dependents><Dependent><FirstName>Jane Smith</FirstName><LastName>Jones</LastName><DOB>1951-02-20</DOB><Gender>Male</Gender><Height_FT>6</Height_FT><Height_IN>9</Height_IN><Weight>221</Weight><Tobacco>false</Tobacco><DependentType>Child</DependentType><Student>true</Student></Dependent><Dependent><FirstName>Sally Smith</FirstName><LastName>Jones</LastName><DOB>1951-02-20</DOB><Gender>Male</Gender><Marital>Married</Marital><Height_FT>7</Height_FT><Height_IN>1</Height_IN><Weight>206</Weight><Tobacco>false</Tobacco><DependentType>Spouse</DependentType></Dependent></Dependents><SelfEmployed>false</SelfEmployed><DUI>false</DUI><ExpectantMother>false</ExpectantMother><MedicalHistory><Relative_Heart>false</Relative_Heart><Relative_Cancer>false</Relative_Cancer><Medication>false</Medication><Medical_Treatment>false</Medical_Treatment><Hospital>false</Hospital><Comments>None</Comments></MedicalHistory><MajorMedical><AIDS_HIV>true</AIDS_HIV><Alcohol_Drug_Abuse>true</Alcohol_Drug_Abuse><Alzheimers_Disease>true</Alzheimers_Disease><Asthma>true</Asthma><Cancer>false</Cancer><Cholesterol>false</Cholesterol><Depression>true</Depression><Diabetes>true</Diabetes><Heart_Disease>false</Heart_Disease><High_Blood_Pressure>false</High_Blood_Pressure><Kidney_Disease>false</Kidney_Disease><Liver_Disease>false</Liver_Disease><Mental_Illness>true</Mental_Illness><Pulmonary_Disease>false</Pulmonary_Disease><Stroke>false</Stroke><Ulcer>true</Ulcer><Vascular_Disease>true</Vascular_Disease><Other_Major_Disease>true</Other_Major_Disease></MajorMedical><CurrentInsurance><CurrentlyInsured>false</CurrentlyInsured></CurrentInsurance><RequestedCoverage>Individual Family</RequestedCoverage></HealthInsurance></InsuranceRequest>

...

Code Block
POST https://dastaging-lm.dev.allwebleads.com/leads/4.0/LeadServiceHttpPost.svc/PricePresentationPostLead HTTP/1.1
Content-Type: application/x-www-form-urlencoded
User-Agent: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.1)
Host: dastaging-lm.dev.allwebleads.com
Content-Length: 3123
Expect: 100-continue

LeadID=677739591&XmlString=<?xml version="1.0" encoding="utf-8"?><InsuranceRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><AffiliateInfo><Username>12696</Username><Password>MyPassword</Password><TrackingCampaign>MyTrackingCampaign</TrackingCampaign><LeadSourceID>SourceID</LeadSourceID><ProductionEnvironment>true</ProductionEnvironment><LeadSourceID></AffiliateInfo><LeadMetaData><LeadBornOnDateTimeUtc>2014-11-11T03:31:21Z</LeadBornOnDateTimeUtc><IpAddress>204.205.123.125</IpAddress><UserAgent>UserAgentTextGoesHere</UserAgent></LeadMetaData><ZipCode>87194</ZipCode><ContactInfo><FirstName>Hadley</FirstName><LastName>Koufacos</LastName><Address>85131 Main St</Address><ZipCode>87194</ZipCode><City>ALBUQUERQUE</City><County>Bernalillo</County><State>NM</State><PhoneDay>7406802874</PhoneDay><PhoneEve>7403071944</PhoneEve><PhoneCell>7406802874</PhoneCell><Email>HadleyKoufacos207610736@test.net</Email><Comment>None</Comment></ContactInfo><HealthInsurance><ApplicantInfo><FirstName>Uriel</FirstName><LastName>Jones</LastName><DOB>1951-02-20</DOB><Gender>Male</Gender><Marital>Married</Marital><Height_FT>6</Height_FT><Height_IN>3</Height_IN><Weight>200</Weight><Tobacco>false</Tobacco><Marital>Married</Marital><Occupation>Other</Occupation><USResidence>true</USResidence><HouseholdSize>7</HouseholdSize><Income>418945878</Income></ApplicantInfo><Dependents><Dependent><FirstName>Jane Smith</FirstName><LastName>Jones</LastName><DOB>1951-02-20</DOB><Gender>Male</Gender><Height_FT>6</Height_FT><Height_IN>9</Height_IN><Weight>221</Weight><Tobacco>false</Tobacco><DependentType>Child</DependentType><Student>true</Student></Dependent><Dependent><FirstName>Sally Smith</FirstName><LastName>Jones</LastName><DOB>1951-02-20</DOB><Gender>Male</Gender><Marital>Married</Marital><Height_FT>7</Height_FT><Height_IN>1</Height_IN><Weight>206</Weight><Tobacco>false</Tobacco><DependentType>Spouse</DependentType></Dependent></Dependents><SelfEmployed>false</SelfEmployed><DUI>false</DUI><ExpectantMother>false</ExpectantMother><MedicalHistory><Relative_Heart>false</Relative_Heart><Relative_Cancer>false</Relative_Cancer><Medication>false</Medication><Medical_Treatment>false</Medical_Treatment><Hospital>false</Hospital><Comments>None</Comments></MedicalHistory><MajorMedical><AIDS_HIV>true</AIDS_HIV><Alcohol_Drug_Abuse>true</Alcohol_Drug_Abuse><Alzheimers_Disease>true</Alzheimers_Disease><Asthma>true</Asthma><Cancer>false</Cancer><Cholesterol>false</Cholesterol><Depression>true</Depression><Diabetes>true</Diabetes><Heart_Disease>false</Heart_Disease><High_Blood_Pressure>false</High_Blood_Pressure><Kidney_Disease>false</Kidney_Disease><Liver_Disease>false</Liver_Disease><Mental_Illness>true</Mental_Illness><Pulmonary_Disease>false</Pulmonary_Disease><Stroke>false</Stroke><Ulcer>true</Ulcer><Vascular_Disease>true</Vascular_Disease><Other_Major_Disease>true</Other_Major_Disease></MajorMedical><CurrentInsurance><CurrentlyInsured>false</CurrentlyInsured></CurrentInsurance><RequestedCoverage>Individual Family</RequestedCoverage></HealthInsurance></InsuranceRequest>

...