Versions Compared

Key

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

Anchor
_tocTop
_tocTop

Table of Contents
maxLevel6
outlinetrue
locationtop
stylenone
typelist

Document Info

Contact Information

...

Company Address

Business Contacts

Technical Contacts

All Web Leads, Inc.
7300 FM 2222
Bldg 2 Ste 100
Austin, TX 78730
Office: 888-522-7355

J.R. Attick
Vice President, Sales 
jeremy.attick@allwebleads.com
Office: 512-279-3115 
Mobile: 512-826-1420 

Kenneth Armond Patrick Jean
Stephen Connolly
Software Engineer
PartnerIntegrations@allwebleads.com

Revision History

Back To Contents

Date

Rev.

Comments

7/9/2013

1.0

New version of document specific to V1.5 API

8/5/2013

1.1

Updated schema since new fields were added. Updated carrier name list.

12/3/2013

1.2

Added TcpaCompliant element under LeadMetaData node.

3/27/2015

1.3

Added Dynamic Calls Ping Response section with schema and sample rejection responses.

Introduction

Back To Contents


This document details the set of technical requirements expected to be met by any potential Data Partner interested in purchasing leads from All Web Leads, Inc. (referred to hereafter as AWL).

...

Protocol Requirements

Back To Contents

AWL requires Data Partners to provide access to an HTTP-based web service that allows AWL to transmit lead data.
AWL systems can support web services supporting secure HTTP POST.

Security Requirements

Back To Contents

AWL imposes at basic set of security requirements upon all Data Partners that receive complete Lead Data from AWL. These security requirements are intended to provide identity and personal information privacy for all end-consumer contacts contained within any lead. These security requirements are also intended to provide basic liability protections for AWL as well as its Data Partners.

...

Quality of Service Requirements

Back To Contents

Reliability and Availability Requirements

...

Performance Requirements

Back To Contents

Web Service Latency

AWL records and closely monitors the latency, in seconds, of every post to a Data Partner web service. AWL requires that all Data Partner web services respond with either a success or failure result in the shortest amount of time possible.

...

Result Code and Acknowledgement Requirements

Back To Contents

AWL requests that any Data Partner web service implementation supports returning a rich set of result codes to communicate as much information as possible.

...

Versioning Requirements

Back To Contents

AWL expects all Data Partner web services to be versioned in an appropriate manner allowing for reliable interoperability. This means that any changes to the Data Partner web service should be coordinated with the AWL technical team. AWL is happy to assist in any way, and to perform the necessary testing to ensure that any upgraded web service will result in the least amount of service disruption as possible (see Testing Requirements).

Testing Requirements

Back To Contents

To ensure a smooth and successful integration, AWL highly recommends that Data Partner web services provide a means by which testing can be performed prior to any production-level integration deployment.

...

Reporting Requirements

Back To Contents

To ensure accurate results, AWL recommends that all Data Partners provide a web-based user interface by which AWL personnel may log in and receive basic reports regarding the status of leads successfully posted to the Data Partner web service.

...