Flexmls RETS Feed api version updated

Hello team,

First of all I would like to thank for your support and helping developer to provide such as nice plugins. We are using your plugin for our website to show property data.
As my client has registered on http://retsgw.flexmls.com/rets2_1/Login website to use their api. Flexmls has sent notification email to my client to update api version. They are saying that api versions below 2_3 will not work after month of may. So we should update api. I just want to confirm from your side that are you working on your plugin to upgrade the api version of 2_3 for your plugin’s users? If yes, then please let me know when you will publish your latest version of plugin, else no then please let me know so that we can customize on our end.
Below is the email notification that we recieved. Please read it and let know if you need anything from my end.

Dear Flexmls RETS Feed Recipient, You are receiving this notice because your email address is attached to a RETS account in the flexmls system. If you are a real estate agent or broker please forward this information to the company that manages your real estate website to ensure that they are aware of the required changes. If you are no longer using your RETS feed this notification can be ignored. Over the coming months we will be decommissioning our rets2_1 RETS server deployment and facilitating a mandatory migration to our latest RETS server deployment (rets2_3). To ensure that your flexmls RETS account remains active and operational you will need to confirm that all of your production RETS processes are pointed to and compatible with our rets2_3 server iteration (http://retsgw.flexmls.com/rets2_3/Login) by the cutoff deadline – June 19th, 2017. Similar to our existing rets2_2 deployment, rets2_3 is fully compliant with both RETS 1.5 and RETS 1.7.2 specifications. As such, we do not anticipate that any moderate or major changes to your existing processes will be required. That being said, we still recommend initiating the migration process as soon as possible to ensure that you are compatible with field changes that could be requested by MLS’s in the immediate future. In summary, any references to “http://retsgw.flexmls.com/rets2_1/Login” in your production MLS data replication/reading processes will need to be replaced with “http://retsgw.flexmls.com/rets2_3/Login” by the cutover deadline of June 19th, 2017. If you are not currently accessing the flexmls RETS server for any purpose this notification can be ignored. An outline of the functionality changes compared to rets2_1 can be found below: * Ability for MLS’s to add a number of additional LIST fields (LIST_173+) to their metadata Our RSS field and data change notification feed will pick up changes to these new fields. If you are not familiar with this tool more information on the data that you can expect to see and how it relates to you can be found on our feed change notification tutorial here: https://www.flexmls.com/developers/rets/tutorials/how-to-receive-notifications-of-feed-changes/. If you have any questions on the migration process or how it pertains to your RETS feed, please contact us. Flexmls RETS Team [email protected]

Thanks
Vishal