For MLSs

The Showing Choice system is a collaboration of CRMLS, Bright MLS, and MRED. We're standing the system up in our markets to solve the specific business problems in the showing product space that all MLSs have been experiencing over the last few years.

We're also releasing Showing Choice as an open source product, so that MLSs across the continent can bring new choice and competition to the showing offerings in their markets.

The Components

Showing Hub

The Showing Hub is the API component and interoperation engine that enables users of any showing vendor to seamlessly request and accept appointments seamlessly with users of other platforms.

An agent goes to their showing platform and enables showings for one of their listings. At that time, the platform registeres with the hub its "ownership" of that listing from a showing perspective.

When another agent wants to show that listing, their platform submits the request to the hub. The "owner" platform is notified via webhook, and responds to accept or decline the request. That response goes back to the seller's platform, and the appointment is confirmed.

The Showing Hub component was originally built by CRMLS, to an API specification designed collaboratively among the three MLSs.

Showing Hub Operations Dashboard

An ops/admin dashboard to give MLS staff monitoring, maintenance, and support tools, and activity monitoring and reporting.

The Operations Dashboard was originally built by Bright MLS.

Slim Client

A lightweight Showing Hub client web app. It serves as both a reference implementation to demonstrate the integration for showing vendors, and as an interface for agents to submit and manage showing appointment requests into the Hub ecosystem.

This is to support agents whose volume might not support hiring a showing platform, but whose business needs still require a way to interact with showing hub vendors.

The Slim Client was originally built by MRED / MLS Grid.

Parts You'll Need to Build

You will need to build an API that can be called from the Hub to pass you pieces of data that are crucial to how the hub works.

When a vendor requests showing authority over a listing, that request is sent to your webhook for approval. The thinking is that you'd have a record of what applications each of your members gives that authority to. The three initial MLSs have plans about how we'll each do that, and we are happy to discuss that.

When you accept such a request, you'll need to update the listing data with the hub Registration ID for that listing. We've aligned on the field name showingHubRegistrationId for that data. This value is how all the other showing providers will know what to "call" a listing on the Hub.