If you want to use one of our products, you will need to get access to the RESO Web API maintained by your MLS. We have a list of RESO Certified Multiple Listings Services here; you can look through that list and see if your MLS is listed there. If not, please contact us.
The RESO Web API is quite different than the classic RETS feed. Many of the MLSs will not pay attention and will just give you the RETS feed, which is not right in this case.
A correct RESO WEB API connection details should have
Client ID, Client Secret, Server Token, Browser Toke, and the URL to do the API queries. Most of the time, the Sever token and the URL for API queries are enough.
Example 1
If your MLS is using Bridge data output as an API provider:
URL: https://api.bridgedataoutput.com/api/v2/OData/test/Property
Server Token: bqb84XXXXXXXXX7lrdy2yjm33ad
Example 2
If your MLS is using Spark API
URL: https://replication.sparkapi.com/Reso/OData/Property/
Server Token: bqb84XXXXXXXXX7lrdy2yjm33ad
If you receive something like the below, we cannot work with it since it is RETS data – see RETS word in the link.
http://xxxxxx.rets.paragonrels.com/rets/fnisrets.aspx/XXXXX/login?rets-version=rets/1.7.2
Username:9xxx35
Password: xxxxg1234
Video tutorials
FAQ
What RESO Web API connection details do I need to provide to use WPResidence products?
To connect via the RESO Web API, you should request the following from your MLS: Client ID, Client Secret, Server Token, Browser Token, and the URL used to run the API (OData) queries.
In many cases, the Server Token and the API query URL are sufficient to get a working connection, but it is best to ask for the full set so nothing is missing.
My MLS sent me RETS login credentials and a RETS URL. Will that work?
No. A RETS feed is not the same as the RESO Web API connection required here. If the link contains the word “RETS” (for example, a Paragon RETS endpoint) and comes with a username and password, that is RETS data and it is not the correct format for this integration.
You should go back to your MLS and specifically request RESO Web API (OData) access details instead.
What does a correct RESO Web API URL look like (Bridge Data Output vs Spark API)?
A RESO Web API connection typically provides an OData URL that points to a resource such as Property, plus a Server Token.
For example, with Bridge Data Output you may receive a URL like https://api.bridgedataoutput.com/api/v2/OData/test/Property. With Spark API you may receive a URL like https://replication.sparkapi.com/Reso/OData/Property/.
How can I check whether my MLS supports RESO Web API access?
You can check the list of RESO Certified Multiple Listing Services referenced in the article and see whether your MLS appears there.
If your MLS is not listed, contact WPResidence so you can confirm options and next steps.
Are there video tutorials that walk through the RESO Web API setup?
Yes. The article includes three video tutorials at the following URLs: https://www.youtube.com/watch?v=rsDgbYC4TyE, https://www.youtube.com/watch?v=P53owlZQrYQ, and https://www.youtube.com/watch?v=R38fY4atll4.
Table of Contents
