For MLSs: What are Deep Links?

Deep Links allow your agents to quickly navigate to pages within RPR from your MLS intranet. For example, agents can go from a listing page on your website to the same property in RPR.

  • You can open the RPR deep link in the user’s existing window, in an entirely new window, or even in an iframe (this can be handled by your developers).

  • If the user is not signed into RPR, they will be prompted to do so (unless SSO is configured), and will then be taken to the requested page.

  • Deep Links can be used in both Commercial and Residential mode, with branding and with Single Sign-On (SSO).

MLS Instructions

Click on the tabs below to see step-by-step instructions.

Manual Developer Instructions (optional)

The easiest way to implement RPR Deep Links is for an MLS staff member to follow the MLS Instructions within this article. MLS staff will use the Deep Link generator tool to quickly and easily create customized deep links that are then pasted into your website code, dynamically changing the query string parameters as appropriate based on the user’s selections. (An RPR MLS Support person can help you generate deep links if you need assistance.) Or manually construct the deep links using the instructions below:
  • Start with the base link: https:/

  • Determine if you have RPR branding. If so, you will need to add cbcode= to the querystring.

  • Determine if you have Single Sign-On (SSO) in place with RPR. If so, add ssocode= to the querystring.

  • Add additional parameters to the query string to return the specific data you’re looking for. Click on the links below to learn more.

  • ApMode (determines whether RPR displays residential or commercial data and functionality)
    • Residential (default)
    • Commercial
  • Action
    • Search
  • SearchType
    • 1 = All Properties search results
    • 2 = For Sale search results
    • 3 = Neighborhood search results
  • ResultType
    • 1 = List View
    • 2 = Map View
  • Query
    • City, State and/or ZIP
    • Neighborhood, City, State and/or ZIP
    • Street Name, City, State and/or ZIP
    • Street Number Range, StreetName, City, State and/or ZIP
    • Full property address is also supported, but we recommend using a PropertyDetails action as noted below.
  • Owner (last name | last name, first name | first name last name)
  • Examples:
  • ApMode
    • Residential (default)
    • Commercial
      • If the property class is unavailable, we will default to residential
      • If commercial mode is passed, the app opens to the home page in commercial mode
  • Action
    • Market Trends
  • Location: query=[property address or place]
    • Property address example: “Query=8736%20Venice%20Blvd%2C%20Los%20Angeles%2C%20CA%2090034”
      • If a property address is passed, use the property ZIP code as the location.
    • Location example: ““Query=Los%20Angeles%2C%20CA%2090034”
  • Note: other parameters like sso code, cb-code, etc.. are not called out in this spec, but will work the same as existing


Developer Tips

Click on the links below. 

  • If you do an APN search, you must also specify a location: an area in the Query parameter or a StateCountyFIPS code in the FIPS parameter.
  • If you search by property address, it’s best to use an address that has been passed through an address standardizer. If that isn’t available, make sure the address is as accurate as possible and that it is formatted as closely as possible to USPS standards.
  • When a property address or area is specified but not uniquely identified by RPR, we will display a “Did you mean” dialog box where the user can choose from among several options. This is a feature, and it occurs for legitimate reasons (such as when the Query parameter includes only a ZIP code, but that ZIP code matches not only the real ZIP but also a number of other listing IDs across the country).

All query string values must be URL-encoded, otherwise you may experience very unexpected results.  This is because some common characters in property addresses, namely the # unit symbol, are restricted HTML commands.  You can use a number of internet tools to URLencode/URLdecode your parameters (, but please remember to not URLencode the entire URL (such as the http:// part, unless you’re passing that full URL into a redirection mechanism on your website).

  • space ( ): %20 or + (browsers usually encode this automatically)
  • comma (,): %2C (browsers usually encode this automatically)
  • semicolon (;): %3B
  • question mark (?): %3F
  • slash (/): %2F
  • colon (:): %3A
  • hash (#): %23
  • ampersand (&): %26
  • equals (=): %3D
  • plus (+): %2B
  • US currency ($): %24
  • percent (%): %25
  • less than (<): %3C
  • greater than (>): %3E
  • tilde (~): %7E

An example with cobrand and SSO support would be:, CA 92604&cbcode=&ssocode=

(this link will not work without modifying cbcode and ssocode)

Frequently Asked Questions

Click on the links below

You do not need to provide Single Sign-On (SSO) to use RPR Deep Links.

Your website developer will need to write a piece of code to pass the appropriate variable (property address, geography, school, etc) to the Deep Link to make it functional.

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!

Popular Articles

Recent Articles