This information is for organizations that have a strong partnership with either the REALTORS® Association of Edmonton. Our transition to the Paragon MLS® system will happen on Tuesday, November 17, 2015.
Q: What is happening?
A: Later this year, the REALTORS® Association of Edmonton will be migrating to the Paragon MLS® system, a product of Black Knight Financial Services (www.bkfs.com).
Q: When is it happening?
A: The Paragon MLS® System began running parallel with MLXchange and Fusion mid-September.
Q: How does this affect my access to RETS?
A: Access to our current Real Estate Transaction Standard (RETS) servers will continue to be available until our cutover to Paragon (November 17), and the new Paragon RETS servers will also come online with a staggered timeline. The Paragon servers were made available for testing mid-September.
Q: How are MLS® numbers affected?
A: MLS® numbers will now begin with “E4”.
Q: Is there a way to search by office or agent ID?
A: Yes, each agent and office record contains the visible Agent/Office ID and a Hidden ID. You can query any RETS property resource by agent or office using the hidden ID for these fields. You can also query the Agent or Office RETS resource by the Agent or Office ID to find the corresponding Hidden ID. Then, in the property resources you can query for listings using the listing agent field L_ListAgent1 and the office field L_ListOffice1.
Q: Is there a specific RETS client we should use?
A: Any RETS client that is compatible with the RESO 1.7.2 standard should work fine. Many have found success with RETS Connector, Conduit, and EZ Rets, among others, and http://www.reso.org has several free RETS clients listed for use. Our RETS servers are intended to be used with any client interchangeably, and currently DIGEST is supported over HTTP, and BASIC over HTTPS.
Q: Does the RETS server support offset?
A: The Paragon RETS servers meet all RESO requirements including support of offset functionality.
Q: How do we get listings that belong to members who are a secondary agent on the listing?
A: At present, you can query the property resources for any of the available list agent or list offices, and Paragon supports up to 3 places for each. To query for all listings where the agent is the secondary agent, simply find the Hidden ID for the user, then query the property resource using the L_ListAgent2 field.
Q: How often will your data be updated?
A: During the parallel period, data will be updated close to real-time, and as often as hourly. After cutover, the RETS servers will pull from the live database so all RETS data will be updated in real-time.
Q: How do I make a basic request for listing data?
A: Many of the RETS clients available make the process very user-friendly by providing a step-by-step setup of the query. If you aren’t using a RETS client that has that feature or you would like to know more about the DMQL structure and syntax, there are many guides and tutorials available online and the entire RESO standards definition document can be found at reso.org. Once the initial RETS servers are set up we will be able to provide the field names so you will know how to make a basic request.
Q: I cannot see a metadata URL in the login response.
A: Please verify that you are using the user agent that has been assigned to you.
Q: I am having issues with User-agent authentication failures.
A: Our new server requires that you calculate a new RETS-UA-Authorization token after you receive a session ID. Additionally, creating the authorization token requires the use of the full user agent, including the version.
A sample PHP library that we have verified to work with our server can be found here: RETS php. This library differs from our previous libraries as it requires libcurl installed as part of your PHP install. This RETS.php was used in conjunction with this Sample File which logs in, queries for metadata and retrieves one property.
Mapping document for residential and commercial vendors: RES_Field_Map
For more resources on RETS, see www.reso.org.