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 here a list of RESO Certified Multiple Listings Services, and 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 MLS’s 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 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 below, we will not be able to 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

 

 

 

 

No comment yet, add your voice below!


Add a Comment

Your email address will not be published. Required fields are marked *