Address to valuation
A 4-step recipe with Landcor Data. We can help you get access.
Recipe · 4 steps
Address to valuation
with Landcor Data · Real Estate Valuation & Appraisal Management
Address string in, AVM valuation range and history out.
- Search by address filters. All five filters are optional in the contract, so at minimum supply street_name plus street_number or postal_code — an unfiltered call is legal and returns an unbounded array with no pagination.
- Full property detail. The response is a fixed composition of seven sections — there is no expand or fields parameter, you always receive all of it.
- Current AVM low/high band. Use this operation, not GET /valuationRange/{pid}/updates — the spec states the updates endpoint now mirrors this one and returns the identical payload. Raises an undeclared 404 when no valuation record exists for
- Chronological valuation snapshots. Also raises an undeclared 404 when no history exists.
What you'll need to have ready
- street_name: Street name to search on, e.g. "Sixth".
- street_number: Street number, e.g. "313".
- postal_code: BC postal code, e.g. "V3L 3A7".
- unit_number
- street_direction
For your developer
Arazzo workflow landcor:address-to-valuation, 4 operations: search_property_property_search_get → read_property_property__pid__get → read_valuation_range_valuationRange__pid__get → read_valuation_history_valuationRange__pid__history_get. Specs on APIs.io.