This Provider Implementation Guide provides the information required for a successful implementation of Title API Integration for receiving and returning Abstractor orders and order status from Direct2Title.

This document is created, maintained, and distributed by Avanze Tech Labs Inc. to communicate the implementation requirements to its customers. Avanze supports the contents included in the Provider Implementation Guide when the order originates from Direct2Title.

HTTP Post

The HTTP Post Method may be implemented for the purpose of inbound event transmission. A Client can send files via HTTP and will receive an XML Response informing them of the status of their submission. This is most frequently used in integrations for the posting of orders from customers and completed documents from service Abstractors. HTTP Posting can also be used as a delivery method for integration partners who choose to receive files via HTTP. HTTPS or SSL (Secure Sockets Layer) is the most common implementation of this method, due to SSL’s security benefits.

Integration partners may also choose to develop an HTTP Receiver of their own, in which they would receive via HTTP Post.

Following URL will be used by integration Client to post inbound events to STACX. API application which will route the events to STACX application.

https://avanzeapi.com/stacx/OrgCode

Authorization through POST Parameters

Two parameters are required in order submit requests through HTTPs POST.

username = [USER]

username = [PASSWORD]

Username and password value used to authenticate incoming request. These values are defined in STACX. API application for each integrator.

Authorization through Header

Instead of sending credentials in plain text through post parameters, an authenticated request includes the Authorization Header Variable. If this header is not included, the request is anonymous and may not succeed against API services.

To authenticate a request, you must encode the combined username and password in the request.

The format for the Authorization header is as follows:

Authorization: Basic [Encoded-Base64-String]

Constructing the Basic Authentication

Username and password are combined into a string "username:password"

The result string is then encoded using Base64

The authorization method and a space "Basic" are then put before the encoded string.

We have many events to process order