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.
Metadata
The identity and technical contract details declared by the specification.
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.
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.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
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.