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="f15f7ad7d61876f2-d47408a5-43c94714-a1a28756-c71a588fa31614269d58ef58"><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="beffaafdc42d65ad-959f4559-4579470a-88bc9d60-6513e03d8359368970e3b4fd"><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="36e20b0c5a5374cb-0849f4d8-495844a1-8be0a5af-b34b849b5f7b2510da6cde73"><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="b2b91ef93886fa9e-3e81d5b1-4c804a49-b57b8b04-3857318047281438cc7c1292"><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="67545f1ee1dcde36-10a1528f-46814247-a2c1a30a-b18afb104a63b34182f52804"><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="e1beae51c9718926-8709cc26-473d474e-b4818491-e88de3fb1c20ac0950fe09d6"><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="6bc365aaff143d88-dc83d24b-4de0451d-9031bf12-e7f5d6994a71bf49c4a8f3f8"><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.9

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

...

Legs Ping Lead API

Back To Contents(Only active on the Staging Environment)

The "Legs Ping Lead" API is used to send leads to the AWL system to receive a bid on certain legs (that we are interested in purchasing. Note that, within the context of shared leads, we refer to each individual potential shared sale of a lead as a leg) that we are interested in purchasing. leg.

The ping process is identical to that of the "Price Presentation Ping Lead" API except the endpoint is different and the response has additional data added to it. In a successful response, the ping response will include the legs (up to 5) that AWL is interested in purchasing. Each leg returned in the ping will have an associated payout with it.

The partner posting can then determine which legs that they want to sell to AWL and they can indicate this in the following Legs Post (see Legs Post Lead API description). When legs with associated payouts are returned, a "LeadID" value is returned which represents a ping session identifier. The ping session identifier may be used in a follow-up "Legs Post Lead" API call to offer selected legs for sale at the previous bid price points. Note that leg bid prices and their ping session identifier is are valid only for up to two minutes.

...

Legs Post Lead API

Back To Contents(Only active on the Staging Environment)

The "Legs Post Lead" API is used to offer legs for a given lead to for sale after those legs have successfully been bid upon by the AWL system via a previous call to the "Legs Ping Lead" API.

...