Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Date

Rev.

Comments

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="a613c6ae52787bbf-c0b35d3b-4472473a-a059b14a-a5a2a6e52cfea416c8ea02d0"><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

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

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

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="e8d527d04563f35d-300b661f-49fc4cbe-92a38a6a-1a716975df6238cf63ba9211"><ac:plain-text-body><![CDATA[

4/07/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="f4206a85461afb4a-06e370ab-41a742bc-98e5b176-a1b99a188b85eeae87fddc9a"><ac:plain-text-body><![CDATA[

4/13/2011

4.2

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

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

<ac:structured-macro ac:name="unmigrated-wiki-markup" ac:schema-version="1" ac:macro-id="0c558330b14a2118-843d175a-47da4372-b9a09003-5ccf83b8a876b52d3bdf7785"><ac:plain-text-body><![CDATA[

4/25/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="365aba03eb3887fb-c61369e4-4ccb47a0-9881a5b2-7cc12503a5396ab5108e6d4a"><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="8df8a55178ed1096-1cd3b791-464a4bc3-9f4681e0-c12755ca066b9eda16163611"><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="4a7869f8a809be76-0fe6ad22-45584c1d-992582b1-4fd58bdd3f00816a4b648c40"><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

...

  • 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
    • The ProductionEnvironment element under the AffiliateInfo node should also be omitted

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
    • The ProductionEnvironment element under the AffiliateInfo node should be omitted

Example HTTP POST Data Payload

...

  • 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 ProductionEnvironment element under the AffiliateInfo node should be omitted

Example HTTP POST Data Payload

...

  • 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 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
    • The ProductionEnvironment element under the AffiliateInfo node should also be omitted

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.
    • The ProductionEnvironment element under the AffiliateInfo node should be omitted

Relevant schemas:

Lead Format Schema
API Response Schema

...