OrderService
Click here for a complete list of operations.
OrderDateDown
Order a Date Down (File Update/Bring To Date) for an order that has previously been created.
ValueCheck will supply AdminId, UserName, Password, VCAppId, and VCClientID.
The details of the order can be sent in a custom XML fragment (ValueCheck will need to write a custom parser) or the default ValueCheck Schema can be used.
| AdminID | Admin Identifier provided by ValueCheck. |
| UserID | User Identifier provided by ValueCheck. |
| Password | Password provided by ValueCheck. |
| VCAppID | Application Identifier provided by ValueCheck. |
| VCClientID | Customer Identifier provided by ValueCheck. |
| AccountNum | Customer supplied Identifier to indicate individual user or Account. |
| OrderNum | Unique Order Number assigned to this order. |
| Submitted | Timestamp of this request. |
| Xml | Details of the Request. See below. |
| Name | Description | Required |
| PolicyType | Policy Type | Yes. Consult with ValueCheck for valid values. |
| ClientWebServiceAddress | The URL of the Customer’s Web Service for the ValueCheck Order Processing Engine to post DataDown Ready/Results notifications.
A string of this format is expected: https://www.yourcompany.com/TA_WS/OrderService.asmx
The Client's Web Service should implement the method DateDownReady that is described later in this document. | Only called if configured at ValueCheck to notify that the Date Down is completed. |
| ClientOrderedBy | Further information indicating who is requesting the order (may be overwritten for Officer Code processing by ValueCheck) | |
| PropState | State of the Order | best if supplied - consult ValueCheck for your requirements |
| PropCounty | County of the Order | best if supplied - consult ValueCheck for your requirements |
| PropPin | Parcel number or APN of the Property | No; but very helpful |
| SpecialDocDate | Date of the last Date Down | No. But if supplied best format is YYYY-MM-DD |
| ClientEmail | Email to send custom response for problems or Date Down results that have discovered new documents | No. Consult ValueCheck for your requirements |
| CloserEmail | Email to send custom response of sucessful Date Down results (no problems and no new documents found) | No. Consult ValueCheck for your requirements |
Example of the default Xml for posting a Date Down Order:
<TitleOrder>
<DateDown VCAppId='int' VCClientID='int' AccountNum='string' OrderNum='string'>
<PolicyType>string</PolicyType>
<PropState>string</PropState>
<PropCounty>string</PropCounty>
<PropPin>string</PropPin>
<ClientWebServiceAddress></ClientWebServiceAddress>
<ClientOrderedBy>string</ClientOrderedBy>
<ClientEmail>string</ClientEmail>
<SpecialDocDate>string</SpecialDocDate>
</DateDown>
</TitleOrder>
|
| AccountNumber | The Account Number given in the request. | ||||||
| OrderNumber | The Order Number given in the request. | ||||||
| StsDate | Timestamp of the result. | ||||||
| Sts |
| ||||||
| Description | A textual description of the an error status. OK if all went well. |
Test
The test form is only available for requests from the local machine.SOAP 1.1
The following is a sample SOAP 1.1 request and response. The placeholders shown need to be replaced with actual values.
POST /TA_WS/OrderService.asmx HTTP/1.1
Host: www.valuecheckonline.com
Content-Type: text/xml; charset=utf-8
Content-Length: length
SOAPAction: "http://TitleAutomation.valuecheck.com/OrderDateDown"
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<OrderDateDown xmlns="http://TitleAutomation.valuecheck.com/">
<order>
<AdminID>string</AdminID>
<UserID>string</UserID>
<Password>string</Password>
<VCAppID>int</VCAppID>
<VCClientID>int</VCClientID>
<AccountNum>string</AccountNum>
<OrderNum>string</OrderNum>
<Submitted>dateTime</Submitted>
<Xml>string</Xml>
</order>
</OrderDateDown>
</soap:Body>
</soap:Envelope>
HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8
Content-Length: length
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<OrderDateDownResponse xmlns="http://TitleAutomation.valuecheck.com/">
<OrderDateDownResult />
</OrderDateDownResponse>
</soap:Body>
</soap:Envelope>
SOAP 1.2
The following is a sample SOAP 1.2 request and response. The placeholders shown need to be replaced with actual values.
POST /TA_WS/OrderService.asmx HTTP/1.1
Host: www.valuecheckonline.com
Content-Type: application/soap+xml; charset=utf-8
Content-Length: length
<?xml version="1.0" encoding="utf-8"?>
<soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
<soap12:Body>
<OrderDateDown xmlns="http://TitleAutomation.valuecheck.com/">
<order>
<AdminID>string</AdminID>
<UserID>string</UserID>
<Password>string</Password>
<VCAppID>int</VCAppID>
<VCClientID>int</VCClientID>
<AccountNum>string</AccountNum>
<OrderNum>string</OrderNum>
<Submitted>dateTime</Submitted>
<Xml>string</Xml>
</order>
</OrderDateDown>
</soap12:Body>
</soap12:Envelope>
HTTP/1.1 200 OK
Content-Type: application/soap+xml; charset=utf-8
Content-Length: length
<?xml version="1.0" encoding="utf-8"?>
<soap12:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://www.w3.org/2003/05/soap-envelope">
<soap12:Body>
<OrderDateDownResponse xmlns="http://TitleAutomation.valuecheck.com/">
<OrderDateDownResult />
</OrderDateDownResponse>
</soap12:Body>
</soap12:Envelope>