XML / JSON feed, schemas and examples
Resale Properties
This section describes the different feed formats available for data export. The API currently provides multiple formats designed to support different platforms and integration requirements.
The feed is supplied live (real-time) from the database at the moment it is requested.
For now, requests are limited to three per agency per day, as a daily update is generally sufficient.
This limitation does not apply to agency property feeds, which can be requested without restriction.
The documentation is not available in the feed, the API or the wordpress plugin, these services are designed to show information about new developments on your website to your end customers. Their main objective is to generate interest and capture the attention of potential customers, encouraging them to contact your agency. It is not intended to provide all the project documentation.
In many cases, the documents provided by the marketers or developers contain detailed information, including text and graphics, which could lead a customer to go directly to the sales office without first contacting your agency. Therefore, we want to ensure that the agency is the primary point of contact for potential buyers.
The feed is available in both XML and JSON formats through the following endpoints:
You must provide the IP address of the server that will access the service in order to request and download the MLS property feed.
This requirement does not apply to agency property feeds, which can be accessed without IP restriction.
All requests must include a valid API token as a query parameter:
token=XXXXX
The following query parameters can be used to customize the feed:
https://api.zoddak.com/resales/xml?token=XXXX
https://api.zoddak.com/resales/xml?format=kyero&scope=all&token=XXXX
https://api.zoddak.com/resales/json?scope=all&token=XXXX
This format is specifically designed for integration with the Kyero real estate portal. It follows Kyero’s official specifications, ensuring seamless compatibility for automatic property publishing.
The generic format provides a flexible structure in XML or JSON, intended for custom integrations. It is suitable for developers who need to consume the data in their own applications or transform it into other formats.
The system is designed to be extensible, allowing additional feed formats to be introduced as needed for future integrations or third-party platforms. This ensures the API can evolve without impacting existing formats.