RETS

RETS Vendor Help

Real Estate Standards Organization Website

Vist the RESO site for detailed information and resources for RETS

 

BKMLS RETS Vendor Support Site

Access our FAQ and Support site! BK MLS staff moderate this site and respond to posts in this forum.

 

What is RETS?

RETS stands for Real Estate Transaction Standard and it is the agreed upon “rules of the road” for data transfer in the Real Estate market.

For additional information please review the following address provided by RETS.ORG to resolve many of your questions regarding RETS. http://www.reso.org/rets

Problem:


Do I need a RETS client to access the data?

Solution:

In order to view and harvest the data, a RETS client is required. Please review RETS.ORG for more information.

Problem:

The vendor is not sure which RETS client they should use to access Paragon RETS.

Solution:

There are a multitude of RETS clients available.  We do not support the use of any specific RETS clients however many vendors utilize the following clients. 

Examples:  ezRETS, RETS Connector.

Please review http://www.reso.org/clients for more information.

 

Problem:


The RETS vendor is receiving a similar message to this error:

"Status code (401) Invalid Username/Password combination" error when attempting to connect to the RETS server. 

Solution:

There are 3 causes for a vendor receiving this error

A)    Please ensure the vendor is using the correct username and password combination. NOTE:  Usernames and Passwords are CASE SENSITIVE in RETS. The correct username/password combination can only be viewed or changed by the local board staff.

B)     If  “Force Password Change at Next Login” is checked in the agent record for the vendor, it needs to be unchecked. This setting can only be changed by the local board staff. NOTE to board staff:   If you utilize an automated periodic password change procedure, please speak to your SSM about exempting certain users from this process.

C)     In the agent record there is a section called “Allowed Paragon Client”. If RETS is not selected, then the vendor will be unable to access the RETS server. NOTE:  This setting can only be changed by the local board staff.

 

Problem:


The vendor is receiving a similar message to below errors.

<RETS-STATUS ReplyCode="20207" ReplyText="Unauthorized Query. You are not authorized to access class [X] in resource [Y]." />

</RETS>

Solution:

The vendor was trying to access Resources or a field not included in their profile as designated by the MLS. Depending on the exact error message in place of X and Y, this can be as simple as a field not being allowed in their RETS profile or an entire RESOURCE/CLASS. NOTE: While LPS staff can assist with identifying the exact issue and will facilitate with the MLS, ultimately it can only be resolved with the approval of the local board staff.

 

Problem:


The vendor attempts to access the RETS URL and receives only:

<RETS ReplyCode="0" ReplyText="Login Request">

<RETS-RESPONSE>

MemberName=User Account

User= User id

Broker=1,1

MetadataVersion=12.8.34035

MinMetadataVersion=12.8.34035

TimeoutSeconds=1800

GetMetadata=/rets/fnisrets.aspx/CLS/GetMetadata

GetObject=/rets/fnisrets.aspx/CLS/getobject

Login=/rets/fnisrets.aspx/CLS/login

Logout=/rets/fnisrets.aspx/CLS/logout

Search=/rets/fnisrets.aspx/CLS/search

</RETS-RESPONSE>

</RETS>

 

Solution :

This response indicates the RETS URL is working correctly.  The vendor is attempting to login to RETS via a standard web browser. This is not supported and requires a RETS client in order to access, query, and pull the RETS data.

 

Problem: 

Is it possible to limit or restrict photos in a RETS feed?

Solution :

We currently do not have the ability to restrict photos in a RETS feed. The photos are contained in the same Class Resource as the listing data and can be accessed via a “Get Object” procedure. For more information please review RETS.ORG

 

Problem:


Why are listing data pulls limited to 2500 records? Is it possible to raise this limit?

Solution:

The limit of 2500 records is a restriction put in place to protect the users of our Paragon databases. Many vendors run scripts to pull information and a misconfiguration of that script could lead to situation that has the same query being run multiple times in a very short period of time. The limit of 2500 records allows vendors to pull a significant amount of information while still protecting the Paragon user experience.  The limit is not generally configurable and should not be changed above 2500 records.

Vendors can utilize a listing “off-set” to pull the remainder of the listings. For more information please review RETS.ORG

Last modified on Friday, 22 April 2016 17:21