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

Reonomy Search API

Search and resolve commercial real-estate properties.

Reonomy Search API is one of 2 APIs that Reonomy publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Search. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 3 operations across 3 paths, and defines 12 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against a single base URL, https://api.reonomy.com/v2.

3 operations 3 paths 12 schemas 3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://api.reonomy.com/v2
Authentication
HTTP Basic
Contact
Terms of Service
Resource Areas
1

Authentication & Security 1

Reonomy Search API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • basicAuth — HTTP Basic Authentication. The Authorization header carries a base64-encoded accesskey:secretkey access token issued by Reonomy.

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 3 POST. Each is listed below with its method, path, parameters, and response codes.

Search 3

Search and resolve commercial real-estate properties.

POST
/search/summaries
Search for properties
searchSummaries 1 param body → 200401
POST
/search/property-shapes
Retrieve property parcel shapes
searchPropertyShapes body → 200401
POST
/resolve/property
Resolve a property to a Reonomy property ID
resolveProperty body → 200401

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are SearchSettings (7 properties), ResolveRequest (7 properties), SearchRequest (4 properties), DateRange (4 properties). Each schema is shown below with its type and property counts.

MapFilters
object
Geospatial filters applied to the property search.
3 properties
ResolveResponse
object
1 property
DateRange
object
4 properties
SearchResponse
object
3 properties
SearchRequest
object
4 properties
SearchSettings
object
Attribute filters applied to the property search.
7 properties
Range
object
2 properties
LatLon
object
2 properties
Sort
object
2 properties
ResolveRequest
object
Address, geolocation, or place name used to resolve a property.
7 properties
PropertyShapesRequest
object
1 property
SearchSummaryItem
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

reonomy-search-api-openapi.yml Raw ↑

Other APIs Reonomy publishes across the network.

Reonomy Property API
Where this information came from

This is an independent, third-party profile of Reonomy Search 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.