Skip to end of metadata
Go to start of metadata

Contact Information

Back To Contents

Company Address

Business Contacts

Technical Contacts

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

Laura Haggarty
Vice President, National Accounts
laura.haggarty@allwebleads.com
Office: 512-279-3093
Mobile: 512-983-2303

AWL Operations Team Alias
operations@allwebleads.com

Ricky Kwong
Software Engineer
ricky.kwong@allwebleads.com
Direct: 512-279-3106

Jeremy Remington
Director of Platform Software
jeremy.remington@allwebleads.com
Direct: 512-279-3111

Revision History

Back To Contents

Date

Rev.

Comments

1/3/2013

1.0

New Broker Disposition API

Introduction

Back To Contents

This document details the information necessary for broker to submit disposition data by HTTPPOST.

Supporting XML Schema Files

Back To Contents

Technical Overview

Back To Contents

Protocol

Back To Contents

The AWL API is available as a simple HTTP POST API, exposed over SSL. This API can be consumed by almost any HTTP client technology.

Security

Back To Contents

Transport Security

Back To Contents

AWL requires that all Data Affiliates utilize industry-standard SSL/TLS over HTTP (HTTPS) as a transport mechanism. HTTPS provides authentication, message confidentiality, and message integrity at the transport level.

Authentication

Back To Contents

All broker will be assigned a unique customer identifier, an customer username, and a password. The identifier is used internally to uniquely identify the partner, while the customer username and password must be provided in each API call in order to allow AWL to ensure the source of the incoming lead.

Firewall Restriction

Back To Contents

Access to the AWL Lead Disposition API is firewall-restricted. Broker partners must provide an IP address or an IP address range in order for AWL to white-list access. Note that both staging and production IP addresses will be required.

Staging Environment

Back To Contents

AWL provides a dedicated staging environment that partners may use to begin testing their integration with the Broker Dispoistion API.

The staging environment is completely isolated from our production environment, and therefore there are no restrictions on the lead data that can be posted into the system.

Note that the AWL staging environment currently resides on hardware infrastructure that is not as powerful as that used by the AWL production environment. Additionally, some tasks performed in the staging environment are "faked", and therefore will result in different latencies in staging versus production. Essentially, performance within the staging environment should not be considered indicative of the production environment.

If latencies are a concern, additional testing may be performed against the production environment using a restricted set of lead data to ensure that test leads are not inadvertently mixed with live production leads. Note that even when sending test leads into the production environment, certain internal operations can vary with respect to the operations performed on a real live lead. For more information on testing within the production environment, please refer to the "Production Environment" section later in this document.

Staging Environment URL

Back To Contents

The following URLs should be used for the HTTPS POST into the AWL system.

Note that these web service endpoints do not support HTTPS GET, and therefore will provide no useful output if entered into a web browser.

https://dastaging-lm.dev.allwebleads.com/leads/1.0/LeadDispositionServiceHttpPost.svc/PostLeadDisposition

Production Environment

Back To Contents

The AWL production environment is used to receive leads disposition data from brokers.

Production Environment URL

Back To Contents

The following URLs should be used for the HTTPS POST into the AWL system.

Note that these web service endpoints do not support HTTPS GET, and therefore will provide no useful output if entered into a web browser.

https://ws.allwebleads.com/leads/1.0/LeadDispositionServiceHttpPost.svc/PostLeadDisposition

Sample XML

            <?xml version=""1.0"" encoding=""utf-8""?>
            <DispositionRequest xmlns:xsi=""http://www.w3.org/2001/XMLSchema-instance"" xmlns:xsd=""http://www.w3.org/2001/XMLSchema"">
               <CustomerInfo>
                  <Username>12345</Username>
                  <Password>Password</Password>
               </CustomerInfo>
               <Leads>
                  <Lead>
                     <LeadId>1234567</LeadId>
                     <Disposition>Sale</Disposition>
                  </Lead>
               </Leads>
            </DispositionRequest>
  • No labels