There’s certainly been a lot of buzz about the launch of RPR™, but even in advance of that, we’re preparing a public beta of service that will allow MLS organizations to programmatically access much of the rich public records content that RPR uses.
The RPR Public Records Application Programming Interface, or API, is for MLS organizations only, and provides a way for MLS Web applications to “talk” to RPR— requesting data that can then be analyzed and formatted for presentation on your MLS system. This is all done automatically, behind the scenes and transparent to your subscribers. Here are two excellent examples: pulling tax records to auto-populate a listing, or pulling comparable properties for display along side a listing. There are many possibilities! Best of all, you don’t need any problematic data feeds. You simply need development personnel skilled in the implementation of XML web services.
We want your feedback!
One of the challenges with producing a robust and stable API is that it is difficult to know how the entire user base will implement the functionality or the data it returns. Since we are releasing this API as a public beta even before the RPR Web site launches, we focused on a few of the essentials that resulted from talks with several initial MLS organizations:
- Provide data for the auto-population of listing input screens.
- Provide comparable properties for use on MLS property detail pages.
- Provide enough data to generate a property details page.
- Provide links back to MLS-branded pages on RPR for full property details, neighborhood demographics, charting, maps and all the other interactive functionality on RPR.
This API should be out the door sometime in February. We have additional functionality in the pipeline, which we will be deploying over time to support features of the RPR Web site as they are tested and released to NAR’s members.
With that said, we are interested in hearing your wants and needs for our upcoming releases. If you represent an MLS organization, please send your suggestions to us at and we’ll consider them for our API product pipeline.