Architecture

ShowingHub is designed as a RESTful API backed by a SQL Server database. The database does not have the full listing record from the MLS. Rather, it stores only the minimal data required. Any additional data may be found in the RETS or RESO Web API feed.

The API is deployed on an EKS cluster, which can scale as demand fluctuates. Both the API and its data are multi-region enabled, ensuring failover for business continuity.

The diagram below illustrates a high-level view of the data flow. ShowingHub sits at the center, facilitating communication between showing applications and the MLS through the API. Upon triggering an event, ShowingHub sends a webhook to the affected party, passing the EventName and associated data. It is the responsibility of the showing provider to process this data and take appropriate action. The MLS is responsible for approving or rejecting new registrations via an integration with ShowingHub. Keeping the registration and appointment data within ShowingHub up to date is solely the responsibility of the showing providers.