PurposeBack To Home
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.
|2||2 Owner search|
|4||30 Year Search|
|11||Deed Report with Taxes|
|19||One Owner with Full Copies|
|23||Sixty Year Search|
|25||Federal Tax Liens|
|26||Good Stop - BOA|
|31||1 Owner - SB|
|35||Update & Recording|
|37||1 Owner - TX|
|38||32 Year Search|
|39||40 Year Deed Search|
|42||Census Tract Only|
|43||Comprehensive Mortgage Report|
|50||Express Title Policy|
|52||Flood & Census|
|54||Life & Census|
|55||Life of Loan|
|56||Limited Commercial Search|
|77||superior courts - 1 name|
|78||Superior Courts - 2 names|
|79||Superior Courts - misc.|
|80||Tax and Legal|
|84||Vesting and Judgments|
|85||40 Year Deed Search|
D2T. API Connectivity
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.
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:
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.
API Event fields & Description
We have many events to process order
|Event Description||Order Placed|
|Event Definition||Abstractor sends this event to initiate an order request to Client.|
|Event Description||Service Confirmed by Client|
|Event Definition||Client sends this event to Abstractor to inform Abstractor the Client accepts the order request.|
|Event Description||Order Not Accepted by Client|
|Event Definition||Client sends this event to Abstractor to inform Abstractor the Client does not accept the order request.|
|Event Description||Client sends this event to Abstractor to inform Abstractor the Client does not accept the order request.|
|Event Definition||Client sends this event to Abstractor with the order documents.|
|Event Definition||Abstractor and/or Client send this event to provide a comment on an order request.|
|Event Description||Service On Hold|
|Event Definition||Abstractor and/or Client send this event to place the order request on hold. This event pauses the Turn Time clock calculation.|
|Event Description||Service Cancelled|
|Event Definition||Abstractor and/or Client send this event to cancel the order request.|
|Event Description||Service Resumed|
|Event Definition||Abstractor or Client sends this event to resume a service order request that has been delayed or put on hold. This event resumes the Turn Time clock calculation.|
|Event Description||Data File Delivered by Client|
|Event Definition||The Client sends this event to the Abstractor to provide the order data.|
|Event Description||Service Completed|
|Event Definition||The Client sends this event to the Abstractor to notify the Abstractor that the order request is complete. This event stops the Turn Time clock calculation.|