Property JSON and XML Feeds

An agency may already have a website, an internal platform or another established system for presenting property inventory. Re-entering the same records in every destination creates extra work and makes it harder to keep each copy aligned. Property JSON and XML Feeds give that external system an organised way to receive structured property data from MLS RealtyHub while the company keeps the tools and interface it already uses.

One Source Process, Another Working Interface

A property feed is an outbound delivery of supported property records from MLS RealtyHub to an external system. The receiving system may be a company website or a separately developed internal product. Instead of treating the two environments as isolated databases, the feed creates a defined route through which property information can move in a machine-readable form.

JSON and XML are the delivery formats. They allow the receiving team to process records as structured data rather than copy details from pages or rebuild them from spreadsheets. The feed itself does not replace the website, CRM or other destination. It supplies data that the external system must be prepared to receive and use.

The Problem Appears Between Systems

Manual export can look manageable when a company works with a small number of properties. As the inventory changes, the same workflow turns into repeated copying, file preparation and checking. A new price, an availability change or an amended property detail may need to be carried into another system by hand. The operational problem is not simply the amount of data. It is the number of separate versions the team must maintain.

A feed reduces that repeated handling by giving the destination a structured input. It also makes responsibilities clearer: MLS RealtyHub holds the property records used for the feed, while the connected system decides how those records appear and behave in its own interface. The fields and update behaviour depend on the agreed implementation; a feed does not automatically make every item in MLS RealtyHub available to every destination.

What Moves Through the Feed

This capability delivers property data. MLS RealtyHub organises an outbound feed, and the external system receives the agreed records in JSON or XML. The properties, fields and media references included are established during technical scoping. There is no universal schema for every client.

Lead and inquiry data are outside this property feed. MLS RealtyHub may notify users about new inquiries within its workflows, but the property feed does not provide an external transfer of personal, lead or inquiry records. The distinction matters:

1. Property records are the subject of the feed.
2. JSON and XML describe how the structured data is delivered.
3. The receiving system is responsible for reading and using that delivery.
4. Field coverage, access method and refresh schedule are agreed during setup.
5. A property feed does not provide a ready-made connection to any CRM or portal.

A Clean Hand-Off Has Three Owners

The feed works best when each participant has a defined part in the process. The business team decides which approved property inventory needs to appear in the destination. MLS RealtyHub provides the agreed outbound property feed. The external technical team configures its system to receive, map and display the data.

That division prevents a common misunderstanding: access to a feed does not mean MLS RealtyHub controls the destination. A company can keep its own website design or internal interface, but its technical team remains responsible for how the destination processes the feed and what visitors or staff see there.

From a Business Request to a Working Data Route

The implementation depends on the receiving system, so setup begins with scope rather than an assumed connector. A useful request identifies the destination, the business purpose and the property records that need to move. The technical discussion can then establish whether JSON or XML fits the receiving environment and which delivery conditions need to be agreed. A typical scoping sequence is:

1. The company identifies the external website or system that needs property data.
2. The business owner defines which approved property inventory the destination should use.
3. The receiving technical team confirms that it can process JSON or XML.
4. The parties agree on the fields, access method, delivery model and update frequency.
5. The receiving team maps and tests the agreed records before relying on them in production.

The endpoint, authentication method, rate limit, schema and launch time depend on the implementation. The integration team provides the relevant technical details as part of the agreed scope.

Example: Keeping an Agency Website Supplied

Consider an agency that manages property records in MLS RealtyHub but wants to preserve the search experience and branding of its existing website. Its operations lead does not want staff to create the same property twice. The company requests a property feed for the website and identifies the inventory that should be available to that destination.

The agency’s developer reviews the agreed JSON or XML delivery, maps the fields to the website and tests how the site handles each record. Once the connection is approved, the website consumes the structured property data provided through the feed. The feed removes the need to prepare a fresh manual file for each delivery, but the website still needs its own logic for presentation, validation and error handling.

Choose the Connection by the Job

Property feeds sit inside the API, Feeds and Integrations module of MLS RealtyHub, but they are not interchangeable with every capability in that module. The right route depends on what the external system needs to do.

1. Use the standard MLS RealtyHub interface when the team can complete the work inside the platform.
2. Consider API-Lite when a property-only programmatic interface is the better fit for the receiving product.
3. Use a JSON or XML feed when the need is an organised outbound delivery of property records in one of those formats.
4. Discuss the full MLS RealtyHub API when the required scope goes beyond the lighter property-only option and needs additional supported resources.
5. Request a CRM or property portal integration when the business needs a specific connection designed for a named external system. These integrations are available on request, not as universal ready-made connectors.
6. Treat a one-time transfer from an old system as data migration rather than an ongoing feed.

This separation keeps the project focused. A feed solves the delivery problem within its agreed scope; bidirectional synchronisation, a custom integration and migration are separate requirements.

What Your Team Keeps Under Control

Using a feed does not require a company to abandon its external interface. The destination can retain its own design, navigation and user experience. The company also defines the business purpose and approved property scope before the technical connection is configured.

MLS RealtyHub remains the professional operating environment behind the data flow; it is not a broker, intermediary or party to a property transaction. The external system remains a separate environment with its own processing, publishing and access responsibilities.

Prepare These Decisions Before Setup

A productive technical review starts with information from both business and technical owners. The more clearly the destination and intended data use are defined, the easier it is to identify whether a feed is the appropriate mechanism. Bring the following to the discussion:

1. The external system or website that will receive the data.
2. The business purpose of the feed.
3. The property inventory that should be considered for delivery.
4. The receiving team’s preferred format, JSON or XML.
5. The destination’s technical contact.
6. Required fields and media-handling questions.
7. Expected update needs.
8. Any access, testing or launch constraints known to the receiving team.

These inputs support scoping. MLS RealtyHub and the receiving team agree on the available fields, permissions, access, delivery and cadence during setup.

Live Capability, Implementation-Specific Details

Property JSON and XML Feeds are a live MLS RealtyHub capability. They deliver agreed property data outward in JSON or XML for use by another system.

Technical details depend on the implementation. Endpoints, payloads, schemas, authentication, rate limits, retry behaviour, compatibility and refresh frequency are established for the connection. A feed is not a ready-made CRM or portal integration. Discuss the destination and request technical access before planning development.

Plan the Right Property Data Connection

Share the destination, required property scope and preferred format with the MLS RealtyHub integration team. They can confirm whether a JSON or XML feed fits the job and provide the technical information needed for implementation.