The Valuation Firm's Guide To Valex Webservices

Valfirm Endpoint:
https://ws.valex.com.au/soap/lixi/1.3/index.php?n=valfirm&handle

WSDL:
https://ws.valex.com.au/soap/lixi/1.3/index.php?n=valfirm&handle&wsdl

Schema Validation

Long Form XML

Short Form XML

Commercial Valuation Overview

Desktop Products

Methods

Critical Checks

Connect With Us

Other

Receiving the valuation request from ValEx

Before you can make or recieve valuation requests through a webservice you need to have your user account setup to have web services enabled.

Email us if your account is not yet setup.

The Soap Envelope

At valex we use a SOAP webservice which contains a LIXI payload. An example of the soap envelope is found here soap envelope. This soap envelope needs to contain an element AuthHeader which will be used to authentication. The format of the soap header is as follows:

<soap-env:header>
<ns2:authheader>
<username>Username_you_provided_us</username>
<password>Password_you_provided_us<password></ns2:authheader>
</soap-env:header>

This is the soap header we expect when you send a packet to us, and the soap header we send to authenticate against your webservice

Note: We'd very much like to standardize upon one simple existing method for authentication information, as illustrated in the example above. As such, we're unable to customize the authentication we use in many cases - this would break compatibility with many other clients or valuation firms; or entail a significant amount of work for each party.

Process

  1. When a job that is allocated to you, the job gets added to an outgoing queue.
  2. Once that job gets to the top of the queue, we create an xml lixi packet containing the Valuation Request. It may be one of many different service types
  3. We then place the lixi packet into a soap envelope and make a soap call to your webservice with the authentication headers that you provided to us(username and password).

    The lixi packet is passed in as a parameter to the function submitValuation to an address that you provide us.

  4. You then reply with a soap response indicating success. Read more about success and error messages.

What's critical to parse from orders?

See our list of xpaths for reference.

  • Address
  • ValEx Job Ref
  • Client Loan Ref
  • Borrowers
  • Inspection Contacts, and Contact details
  • Client/Funder name, id.
  • Service type (Shortform, Construction, etc)
  • Additional comments
  • SLA Deadline
  • Urgency flag

Updating the status of a valuation job

After you have recieved the job, you then need to send several different packets to update the ValEx system with information in relation to the job.

For all of these, you call the SOAP method statusUpdate passing in the XML LIXI workflow packet as the parameter to the following address: https://ws.valex.com.au/soap/lixi/1.3.1/service.php?n=valfirm&wsdl

We accept 4 different types of workflow packet:

  • Accepted – This is to notify us that you have decided to accept the job.
  • Assigned – This is to notify us of the details of the valuer you have assigned.
  • Inspected – Once the valuer has inspected the property, you send through a notification with the inspection date.
  • Delayed - This is to notify us of any delays. The delay is sent to ValEx, and the job status is updated with the delay.

As always with any outgoing packets, you need to validate your packet against the XSD in your system to ensure data compatibility.

Sending the completed valuation to ValEx

What's critical to send in a valuation response?

Our Packet tester highlights fields and xpaths.

In general, if it would be in a Property Pro style report, you'll want to send it. We pay specific attention to:

  • Address
  • AMV
  • Photos
  • Valuation Report (PDF) from your system
  • Risk Ratings
  • Securitisation items, comments
  • Additional comments
Reblog this post [with Zemanta]