Developer Documentation
Platform Overview
API Services
Overview Accounts Accounts: Associations Accounts: Metadata Accounts: Profile Appstore: Users Broker Distributions Broker Tours Consumers Consumers: Linked Agents Contacts Contacts: Activity Contacts: Export Contacts: Tags Contacts: Portal Accounts Developers: Identities Developers: Keys Developers: Authorizations Developers: Billing Summary Developers: Change History Developers: Domains Developers: News Feed Webhooks Developers: Roles Developers: Syndications Developers: Templates Developers: Usage Detail Developers: Usage Summary Devices Flexmls: Email Links Flexmls: Listing Meta Origins Flexmls: Listing Meta Translations Flexmls: Listing Meta Field List Translations Flexmls: Listing Reports Flexmls: Listing Updates Flexmls: Mapping Layers IDX IDX Links Listing Carts Listing Carts: Portal/VOW Carts Incomplete Listings Incomplete Listings: Documents Incomplete Listings: Documents Metadata Incomplete Listings: Document Uploads Incomplete Listings: FloPlans Incomplete Listings: Photos Incomplete Listings: Photos Metadata Incomplete Listings: Photo Uploads Incomplete Listings: Rooms Incomplete Listings: Tickets Incomplete Listings: Units Incomplete Listings: Videos Incomplete Listings: Videos Metadata Incomplete Listings: Virtual Tours Incomplete Listings: Virtual Tours Metadata Listings Listings: Clusters Listings: Documents Listings: Documents Metadata Listings: FloPlans Listings: Historical Listings: History Listings: Notes Listings: Search Parameters Listings: Open Houses Listings: Photos Listings: Photos Metadata Listings: Photo Uploads Listings: Document Uploads Listings: Rental Calendar Listings: Rooms Listings: Rules Listings: Tour of Homes Listings: Tickets Listings: Units Listings: Validation Listings: Videos Listings: Videos Metadata Listings: Virtual Tours Listings: Virtual Tours Metadata Listing Meta: Custom Fields Listing Meta: Custom Field Groups Listing Meta: Field Order Listing Meta: Field Relations Listing Meta: Property Types Listing Meta: Rooms Listing Meta: Standard Fields Listing Meta: Units Registered Listings Market Statistics Messages News Feed News Feed: Curation News Feed: Events News Feed: Metadata News Feed: Restrictions News Feed: Schedule News Feed: Settings News Feed: Templates Open Houses Overlays Overlays: Shapes Portals Preferences Properties Properties: Clusters Properties Meta: Standard Fields Saved Searches Saved Searches: Provided Saved Searches: Restrictions Saved Searches: Tags Search Templates: Quick Searches Search Templates: Views Search Templates: Sorts Shared Links System Info System Info: Languages System Info: Search Templates
API Explorer
Supporting Documentation
Terms of Use

RESO Web API Overview

Built within Spark® API is a /Reso/OData endpoint that implements RESO's Web API, and provides data using the RESO Data Dictionary.

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.

  1. Overview
  2. Authorization
  3. Making Requests
    1. Web API Version
    2. Resources
    3. Retrieving Meta Data
    4. Retrieving Data
    5. Request Parameters
  4. Response Description
  5. Replication

1. Overview

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.


2. Authorization

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

  1. Resources
  2. Retrieving Meta Data
  3. Retrieving Data
  4. Request Parameters

Our RESO Web API provides the following distinct endpoints:

Retrieving Meta Data

Metadata is accessible at:$metadata
Retrieving Data

Using the properties resource as our example, all properties can be retrieved at:

… and an individual property can be retrieved at …'<PropertyId>')

<PropertyId> is the same data as StandardFields.ListingKey or Id when using the Spark API listing's service. So, if the listing's Id was 20100000000000000000000000, your request would be:'20100000000000000000000000')

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:'20100000000000000000000000')/Media
Request Parameters

Each service supports some or all of the request parameters documented on our RESO request parameters page.


Response Description

This OData service only responds to JSON format except for the $metadata endpoint.



Special considerations often apply when replicating. If you want to replicate data using our RESO Web API endpoints, please review our replication documentation.