OrderService Web Service

OrderService

Click here for a complete list of operations.

DateDownReady

Used For Example only - non functional on this site.

When configured by ValueCheck to do so, this customer implemented method will be called by the ValueCheck Title Automation Systems when a Date Down Reqeust has been completed.

Notes on usage:

It must be implemented by the customer as an HTTP-SOAP Web Service.
ValueCheck must enable this.
Each Date Down Reqeust that needs notification must have the 'ClientWebServiceAddress' set to the URL of the Web Service that implements this method at the time the operation OrderDateDown is called.

Arguments:

Argument

Description

order

The Order identifier.

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.

Will contain the same information as what was posted with the Order without the authentication credentials.

Sts

Status	Value	Description
1	NoDocs	Date Down was performed and no new postings were found.
2	FoundDocs	Date Down was performed and new postings were found.
-1	NotFound	Unable to find the Order to Date Down
-2	NotSupported	Date Down are not supported in the requested State/County/TitleSystem.
-4	NotAuthorized	Client not authorized for Date Downs.

statusInfo

More infomation about the order. Most likely will contain a textual description about a problem.

DateDownXml

More information about the order in a structure customized for the customer if neeeded. Currently will return this content:

<DateDownInfo>
  <EffectiveDate>yyyy-MM-dd</EffectiveDate>      If not known then the content will be empty
  <SearchSinceDate>yyyy-MM-dd</SearchSinceDate>  If not known then the content will be empty
  <DocId>DocId</DocId>                           The DocId for the Date Down Results. Content will be empty if a data down could not be preformed
                                                               use the DocID in the call to GetImage2 to retrieve the image of the date down.
  <NumDocsFound>int</NumDocsFound>               Number of posted documents discovered in the date down.
  <Message>string</Message>                      Human readable message about the results of the datedown
</DateDownInfo>

Returns: The customer returns a Status Object that contains:

Return	Description
AccountNum	Must be the same as sent in the order.
OrderNum	Must be the same as sent in the order.
Sts	Zero to acknowledge the status update. Non-Zero to indicate a problem.
Description	Textual information about the Sts.
StsDate	TimeStamp of response.

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/DateDownReady"

<?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>
    <DateDownReady xmlns="http://TitleAutomation.valuecheck.com/">
      <order>
        <VCAppID>int</VCAppID>
        <VCClientID>int</VCClientID>
        <AccountNum>string</AccountNum>
        <OrderNum>string</OrderNum>
        <Submitted>dateTime</Submitted>
      </order>
      <status>Unknown or NoDocs or FoundDocs or NotFound or NotSupported or DoesNotExist or NotAuthorized</status>
      <statusInfo>string</statusInfo>
      <DateDownXml>string</DateDownXml>
    </DateDownReady>
  </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>
    <DateDownReadyResponse xmlns="http://TitleAutomation.valuecheck.com/">
      <DateDownReadyResult />
    </DateDownReadyResponse>
  </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>
    <DateDownReady xmlns="http://TitleAutomation.valuecheck.com/">
      <order>
        <VCAppID>int</VCAppID>
        <VCClientID>int</VCClientID>
        <AccountNum>string</AccountNum>
        <OrderNum>string</OrderNum>
        <Submitted>dateTime</Submitted>
      </order>
      <status>Unknown or NoDocs or FoundDocs or NotFound or NotSupported or DoesNotExist or NotAuthorized</status>
      <statusInfo>string</statusInfo>
      <DateDownXml>string</DateDownXml>
    </DateDownReady>
  </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>
    <DateDownReadyResponse xmlns="http://TitleAutomation.valuecheck.com/">
      <DateDownReadyResult />
    </DateDownReadyResponse>
  </soap12:Body>
</soap12:Envelope>