RESO Web API Overview
The documentation we provide does not fully document the RESO Web API itself; rather, it's meant to get you up and running on our implementation of the standard.
- Making Requests
- Response Description
The RESO Web API endpoint is at:
Because the RESO Web endpoint is built on Spark API, you can use the same API keys provided for Spark to access the RESO Web endpoint.
The method for obtaining authorization from end users and making authenticated requests is identical to accessing Spark directly.
See our authentication documentation for more information.
3. Making Requests
Our RESO Web API provides the following distinct endpoints:
Retrieving Meta Data
Metadata is accessible at:
Using the properties resource as our example, all properties can be retrieved at:
… and an individual property can be retrieved at …
<PropertyId> is the same data as
Id when using the Spark API listing's service.
So, if the listing's
20100000000000000000000000, your request would be:
Note that the Media endpoint is accessed as a subresource of listings. So, to find the
media for listing
20100000000000000000000000, your would hit the URI:
Each service supports some or all of the request parameters documented on our RESO request parameters page.
This OData service only responds to JSON format except for the
Special considerations often apply when replicating. If you want to replicate data using our RESO Web API endpoints, please review our replication documentation.