Additions to the flexmls API

by Greg Kilwein on June 13, 2011

in flexmls API

We are happy to announce some additions to the flexmls API. A summary of the changes are as follows:

  • PropertySubType, SubdivisionName, and MLSAreaMinor are new standard fields available in the Listings service.
  • The number of listings that match a query may be retrieved without returning any listing data, with a new _pagination=count parameter.
  • Rooms and unit information is now included in the CustomFields portion of the response from the Listings service.
  • The Contacts service now allows a message to be sent to the agent when a new lead is added.
  • The new listing cart service allows listing carts to be retrieved, edited and searched.
  • The new shared listings service creates a link that allows listings to easily be shared via social networking sites, e-mail, etc.
  • The standard fields service now has a way to find fields and items in those fields’ lists that are nearby a latitude and longitude coordinate. This service is designed for applications that run on a mobile device.
  • The System Info service now returns MLS logo information to help meet MLS requirements in client applications.

As always, we welcome your feedback about these features and hope you find them useful.


Max June 22, 2011 at 12:40 pm

Great additions! Thanks for adding the SubdivisionName into the StandardFields. I also see you added ListingId into the StandardFields as well. This is great, I just didn’t see the later being mentioned on your blog.

I would like to make a couple of suggestions:

1. Could you please version the PHP API client that you host on Git-Hub? A comment at the top of the code would be more than enough, otherwise I had to brows through the Class to see if there is anything new.

2. What do you think about adding “Special Listing Cond” custom field into the standard array and making it searchable as well as offer a list for it? It seems like it would be an awesome additions since in this market it’s very useful to differentiate between foreclosures, short sales and regular sales. Being able to search by the field is useful, but being able to see the listing conditions within search results greatly improves usability IMHO. Take a look at this example of Myrtle Beach properties – all foreclosures and short sales are conveniently marked, so the user can make quicker/better navigational choices.

Max June 23, 2011 at 10:52 am

Just realized the search by ListingId (MLS #) wasn’t added for a single listing request. One of your devs told me this would be added into the next API update. Is this still coming or not really?

Greg Kilwein June 23, 2011 at 2:07 pm

Max, thanks for the comments.

Versioning the PHP API client on GitHub sounds helpful so I’ll mention it to the developer.

Standardizing the special listing condition fields (short sales, etc.) would be useful and meaningful across a variety of MLSs. We’re working out a process to add more standard fields, so I’ve added this idea to the list of standard field suggestions. We’ll need to do some research to see how different MLSs have defined these fields and find a standardized way to represent this information for everyone in the API.

The MLS # request is still slated for an upcoming release. The production API intentionally lags behind the development version of the API, so it may be a few releases before this feature is live.

Thanks again for the feedback!

Max June 24, 2011 at 10:09 am

Thanks for the reply, Greg! Sounds exciting. The current API is definitely more than enough to work with, but I’m looking forward to the future releases 🙂

Comments on this entry are closed.

Previous post:

Next post: