For MLSs: What is the RPR API?

The RPR Application Programming Interface (API), also known as the RPR Tax API, allows your MLS website to programmatically include public records data from RPR right on its own pages.

  • Pre-populate listing input screens with public records data.

  • Generate comparable properties.

  • Display public records data and mortgage information alongside your listings.

Methods

Click on the links below to see the methods available in the RPR API, and the inputs for each method.

Inputs common to all methods:

  • Username:  This is your RPR API username, provided by your account manager.  It is not the same as your RPR website username.
  • Password:  This is the password for your account.
  • Address:  Geographical area, such as:
    • Irvine, CA
    • Irvine, CA 92604
    • 92694
    • Woodbridge in Irvine, CA (this is a neighborhood in Irvine, CA)
  • MinBedrooms:  The minimum number of bedrooms.
  • MinBathrooms:  The minimum number of bathrooms.
  • MinLivingAreaSizeSqFt:  The minimum living area, in sq. ft.
  • MinLotSizeSqFt:  The minimum lot size, in sq. ft.
  • YearBuiltStart:  Year built, starting year.
  • YearBuiltEnd:  Year built, ending year.
  • SoldSinceDate:  YYYY-MM-DD 
  • OwnerName:  The name of the owner, in a format as close to what the county uses in tax records.
  • SortColumn: Sort by any other field in this method.  For example, SoldSince.
  • SortDirection:  The order of the sort column, either descending or ascending.
  • StateCountyFIPS:  This field is reserved for specific use cases, and should not be used unless directed by your RPR API Support representative.
  • You can specify a property address by either address or APN:
    • Address:  A full property address, such as 1 Live Oak, Irvine, CA
    • APN:  An official parcel number, such as 451-683-01. When the parcel number is used, you must also specify the county/state, city/state, or zip in the Address field.
  • NumberOfComps:  The number of comparable properties to return with the subject property.

See the input schema.

Frequently Asked Questions

Click on the links below

The RPR API is only available for MLS organizations. Request access to the RPR API.

We are sorry but, The RPR API is not available for brokers or agents.

  • Pre-populate listing input screens.
  • Generate comparable properties.
  • Display public records data and mortgage information alongside your listings.
  • GetProperties, for returning multiple property summary records (search results).
  • GetPropertyDetails, for returning details about a subject property.
  • GetComparables, for returning comparable properties.

Your website makes a SOAP (Simple Object Access Protocol) web service call to one of the methods of the RPR API, specifying the appropriate username, password and query parameters. The API then looks up that data and returns it to you in the form of XML. Your website then transforms that XML into HTML for display on your website.

The API has nationwide coverage, but the coverage and detail level of the various data types varies by location. Please see your RPR account representative for coverage information for your area.

The following data types are generally available nationwide, but coverage and detail level varies by location:

  • Public Records (assessment data)
  • Deed
  • SAM (stand-alone mortgage records)

The following data are not included in the API for licensing reasons:

  • Estimated Values (RVM® and AVM)
  • Listings data
  • Neighborhood demographics
  • Weather data
  • Notice of Default (NOD) data
  • School Information
  • Data feeds; an API is meant for interactive querying, not the bulk delivery of data.

The RPR API is simple, but you need an application platform that can integrate SOAP-based XML web services as well as application programmers experienced in working with web services.

Ideally, specify an Address of , , and then the APN as usual.  If you must specify a city name, then you can also specify the optional parameter for StateCountyFIPS (format: 12345).  This is a secondary filter that will take the results from your city search and further filter them by the specified county.  Please ensure that your StateCountyFIPS is correct for that county, because you will not get any search results if you specify the wrong value.

There is no simple http test interface to use, but your development platform should include a tool to access these web services. For Visual Studio users, the WCF Test Client is available within the Visual Studio program files directory.

Personnel authorized to enter into agreements on behalf of the MLS can request an API account at https://blog.narrpr.com/tax-api. If access is approved, you should get your API account within three business days.

If you represent a technology vendor and have multiple clients interested in the API, each client must individually accept our terms of use and receive their individual API account. The appropriate credentials must then be used by your system to request RPR data on behalf of the MLS.  Account sharing, for any purpose whatsoever, is strictly forbidden.

RPR maintains the operation of the API and the data therein, but we cannot provide support to developers trying to integrate the API. Please ensure that your developers are experienced with SOAP-based XML web services, and ideally that they also have the ability to integrate an API defensively so API problems do not cause errors on your website if the RPR API has a hiccup.

Changes in the RPR API can require changes in the codebase of your own application.  This means that the release process for the API is much more involved, for both parties.  Generally, the process is as follows:

  1. RPR will attempt to provide the MLS community with release notes regarding the changes to the API just prior to the release to QA.
  2. API users will be requested to test their applications against the API in our QA environment.
    1. If the MLS API integration functions as-is, no deployment challenges are involved.
    2. If the MLS API integration does not function as expected, code changes may be required on one side or another.  It is therefore critical that testing be performed as early in the QA release cycle as possible (often we only have 2-3 days to identify and address bugs).  Additionally, once functionality is restored it will be necessary for the MLS to coordinate their website patch with RPR’s release date.  Defensive coding should be added where possible, to reduce the probability of failures in the future.
  3. RPR will notify users that a new production release has been deployed.
  4. API users should re-test their applications in their production environment once the RPR API release has been deployed.

The API is designed to be a highly available enterprise-class platform. However, it is always wise to integrate the API into your website in such a way that an API outage or error does not adversely impact your website. Your programmers should therefore implement defensive coding practices to minimize these impacts.  It is also recommended that you employ a configuration switch that allows you to turn API integration on and off on-the-fly.

Please send your ideas/comments/feedback to APISupport@narrpr.com.

Currently, the only method to get data from RPR is via the API. This is by far our preferred delivery method for several reasons:

  • It’s interactive, so you only get back the data you request.
  • It’s fast and reliable.
  • There are no disk storage requirements (our public records data spans many, many terabytes).
  • There are no complicated transfer mechanisms for large data files to build and maintain.
  • All the heavy lifting is done by RPR. There’s no need to optimize database calls, etc.
  • The API is always in sync with the main RPR website.

Need Help?

If you need additional assistance, contact RPR Member Support at (877) 977-7576 or open a Live Chat from any page of the website.

Share This Story, Choose Your Platform!