How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Landcor Property API

The Landcor Property API is a live REST service on api.landcor.com that publishes a valid OpenAPI 3.1.0 contract titled "Landcor Property API" version 0.1.0, served anonymously at https://api.landcor.com/openapi.json (HTTP 200, 47,840 bytes, fetched 2026-07-26) with interactive Swagger UI at /docs and ReDoc at /redoc. It exposes twelve operations across four tags. Property covers GET /property/search (address filters for unit number, street direction, street number, street name and postal code), GET /property/{pid} for full property detail keyed on the Landcor PID in xxx-xxx-xxx format, GET /property/{pid}/report/pdf which returns a base64-encoded, password-protected PDF report, and GET /address/autocomplete. Valuation covers GET /valuationRange/{pid}, GET /valuationRange/{pid}/updates, GET /valuationRange/{pid}/history, POST /valuation/ltv-check for loan-to-value comparison against the AVM value, and GET /valuation/neighbourhood/{neighbourhood_code}/{unit_type_code}/sales for aggregated monthly or rolling-three-month neighbourhood sales series. Comparables covers GET /comparables/{pid}. AVM Summary covers POST /generate-avm-summary, which generates a narrative summary from Landcor AVM data. Health covers GET /health, the only unauthenticated operation, which returns {"status":"ok"}. Authentication is a single HTTPBearer security scheme; every other operation declares it and returns HTTP 401 with {"detail":"Missing token"} when called anonymously, verified against /property/search, /address/autocomplete and /valuationRange/{pid} on 2026-07-26. The contract is public but the credentials are not: Landcor publishes no developer portal, no key issuance page, no API pricing and no API terms, and does not reference api.landcor.com anywhere on landcor.com, so tokens are obtainable only through a direct commercial arrangement with the company. The specification's own operation descriptions disclose the implementation behind it, naming the stored procedure USP_SEARCH_SERVICE_PROPERTY and a legacy Landcor SOAP webservice that produces the PDF report, which is recorded here as harvested fact rather than as documentation Landcor intended to publish.

Landcor Property API is published by Landcor Data on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Property, Valuation, AVM, Comparables, and Real-Estate. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 12 operations across 12 paths, organized into 5 resource areas, and defines 38 schemas. It is described by OpenAPI 3.1.0, at version 0.1.0.

Requests are made against the base URL https://api.landcor.com.

12 operations 12 paths 38 schemas 10 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
0.1.0
Base URL
https://api.landcor.com
Authentication
HTTP Bearer
Resource Areas
5

Authentication & Security 1

Landcor Property API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (HTTPBearer).

Paths & Operations 12

Across 12 paths, the API surfaces 12 operations — 10 GET, 2 POST. They span 5 resource areas: Health, Property, Valuation, Comparables, AVM Summary. Each is listed below with its method, path, parameters, and response codes.

Health 1
GET
/health
Service health check
health_check_health_get → 200
Property 4
GET
/property/search
Search for properties using the stored procedure address filters.
search_property_property_search_get 5 params → 200422
GET
/property/{pid}
Retrieve detailed information for a property.
read_property_property__pid__get 1 param → 200422
GET
/property/{pid}/report/pdf
Return the encrypted PDF report for a property.
read_property_pdf_property__pid__report_pdf_get 1 param → 200422
GET
/address/autocomplete
Autocomplete address lookup
autocomplete_address_address_autocomplete_get 2 params → 200422
Valuation 5
GET
/valuationRange/{pid}
Retrieve valuation range information for a property.
read_valuation_range_valuationRange__pid__get 1 param → 200422
GET
/valuationRange/{pid}/updates
Return the valuation range for compatibility with the updates endpoint.
read_property_monthly_update_valuationRange__pid__updates_get 1 param → 200422
GET
/valuationRange/{pid}/history
Retrieve the complete valuation history for a property.
read_valuation_history_valuationRange__pid__history_get 1 param → 200422
POST
/valuation/ltv-check
Compare a property's AVM value against a provided LTV amount.
run_ltv_check_valuation_ltv_check_post body → 200422
GET
/valuation/neighbourhood/{neighbourhood_code}/{unit_type_code}/sales
Retrieve aggregated neighbourhood sales data.
read_neighbourhood_sales_series_valuation_neighbourhood__neighbourhood_code___unit_type_code__sales_get 5 params → 200422
Comparables 1
GET
/comparables/{pid}
Retrieve properties comparable to the given PID.
read_comparables_comparables__pid__get 1 param → 200422
AVM Summary 1
POST
/generate-avm-summary
Generate Avm Summary
generate_avm_summary_generate_avm_summary_post body → 200422

Schemas 38

The contract defines 38 schemas that model the data the API accepts and returns. The most detailed are ExteriorDataSection (26 properties), SubjectProperty (23 properties), ComparableSale (19 properties), PropertyUsageSection (17 properties). Each schema is shown below with its type and property counts.

AssessmentYear
object
4 properties 1 required
AutocompleteResponse
object
Response containing address autocomplete suggestions.
2 properties 2 required
BCAssessmentSection
object
Valuation metrics sourced from BC Assessment.
13 properties
ClimateEvent
object
4 properties
ClimateEvents
object
2 properties
ComparableProperty
object
Comparable property details grouped into shared property sections.
9 properties
ComparableSale
object
Comparable sale with full underwriting detail.
19 properties
ComparablesResponse
object
Response schema for comparable properties.
2 properties 2 required
ExteriorDataSection
object
Exterior construction, site dimensions, parking, and amenity data.
26 properties
HTTPValidationError
object
1 property
HistoricalSale
object
4 properties
InteriorDataSection
object
Interior counts, configuration details, and square-footage metrics.
15 properties
LTVCheckRequest
object
Request body for comparing a property's AVM against an LTV amount.
2 properties 2 required
LTVCheckResponse
object
Outcome of comparing a property's AVM against an LTV amount.
4 properties 4 required
LandcorAVMSummaryRequest
object
Request body for generating an AVM narrative summary.
10 properties
LandcorAVMSummaryResponse
object
Response payload returned by the narrative generation endpoint.
2 properties 2 required
NeighbourhoodInsights
object
4 properties
NeighbourhoodSalesPoint
object
Aggregated sales metrics for a neighbourhood and unit type.
7 properties 2 required
NeighbourhoodSalesSeriesResponse
object
Response wrapper for neighbourhood sales series data.
3 properties 2 required
NeighbourhoodScores
object
3 properties
NeighbourhoodValueRange
object
3 properties
OtherSection
object
Additional jurisdictional and legal identifiers.
15 properties
Permit
object
6 properties
PermitHistory
object
2 properties
PropertyAddressMetadata
object
Formatted address details and related map metadata.
11 properties
PropertyReportPdfResponse
object
Encrypted PDF report returned by the legacy Landcor web service.
6 properties 5 required
PropertyResponse
object
All available property details for a single PID.
8 properties 7 required
PropertySaleSection
object
Latest sale metadata for the property.
2 properties
PropertySearchResult
object
Normalized subset of fields returned from the property search.
4 properties
PropertyUsageSection
object
Classification and jurisdiction metadata describing how the parcel is used.
17 properties
SubjectProperty
object
Physical, legal and locational attributes of the subject property.
23 properties
ValidationError
object
3 properties 3 required
ValidationResult
object
Result of validating a generated narrative.
2 properties 1 required
ValuationChange
object
2 properties
ValuationHistoryPoint
object
Single valuation history snapshot for a property.
3 properties 1 required
ValuationHistoryResponse
object
Collection of valuation history points for a property.
2 properties 1 required
ValuationMeta
object
Headline valuation outputs and methodology.
7 properties
ValuationRangeResponse
object
Valuation range for a property.
3 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

landcor-property-api-openapi.json Raw ↑
Where this information came from

This is an independent, third-party profile of Landcor Property API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.