Sample Sidebar Module

This is a sample module published to the sidebar_top position, using the -sidebar module class suffix. There is also a sidebar_bottom position below the menu.

Sample Sidebar Module

This is a sample module published to the sidebar_bottom position, using the -sidebar module class suffix. There is also a sidebar_top position below the search.
Update - LoginName

RETS Update - LoginName

Download PDF version of this Notificaiton


June 13, 2015


Dear RETS Vendor,


Black Knight MLS has decided to NOT implement the additional security for accessing the LoginName via RETS in the upcoming June release. After additional feedback and consideration, it has been determined that the security measures will only be required for vendors who need access to the U_Password field.

We apologize for any extra work that this may have caused but it will not be in vain. We plan to eventually phase out non-SSL RETS access and are looking at the end of 2015 as the potential target date. So any work to move to SSL will put you ahead of the game.


During this effort, we discovered that some vendors are using legacy URLs that contain “fnismls” instead of “paragonrels.” In order for the SSL to work (for the vendors who need access to the U_Password field), the RETS URL needs to follow the following format:




We found many that were using the following:



If you require the Password field in your RETS feed you will need to do the following:

1.       Edit your RETS URL to use SSL by adding “s” to “http” and replacing the dot with a dash between the MLSID and “rets.” For example, “http://imls.rets.paragonrels…” will change to “https://imls-rets.paragonrels...

a.       NOTE: If you are using a legacy URL with “,” you need to also change the “fnismls” to “paragonrels” for SSL to work

2.       Have your RETS User-Agent registered by Black Knight MLS. You can do this by sending your RETS User-Agent to John Stock at This can NOT be a generic user-agent such as RETS-Connector/1.2 or librets/1.0. It must be a unique user-agent.

3.       After the User-Agent is registered, include the User-Agent and credentials along with the agent login that you currently using to access RETS for the request.

NOTE: the U_Password field is not exposed to RETS by default. Customers will need to contact their SSM to have the field added and the metadata refreshed. In addition, vendors will undergo a review process by the Black Knight Vendor Management Office to ensure the appropriate protocols are in place for securely storing user password data.



Black Knight MLS Solutions

Last modified on Tuesday, 01 March 2016 21:41