An open XML specification for listings, developments, branches, agents, and high-volume synchronization
Connect detailed listings to projects. Unavailable units remain visible inside the development instead of disappearing without context.
Model multi-branch organizations and agents directly in the feed, with predictable per-listing and per-development contact priority.
Complete XML snapshots are designed for streaming ingestion, bounded-memory parsing, and parallel worker batches.
Content fingerprints detect changes across listing data, attributes, photos, and text without depending on timestamps.
Provide accurate source coordinates while choosing whether users see an exact or approximate public location.
Typed residential and commercial attributes cover property details, amenities, planning zones, accessibility, and more.
RERA XML v2 turns a flat property export into a reusable real estate data model. It carries not only listings, but also the developments they belong to, the organizations that own them, the branches responsible for them, and the agents who represent them.
The specification is designed for real operational problems that are often left to private integration code: large inventories, contact routing, unit availability, location privacy, and reliable change detection.
A development is a reusable project entity. Every sellable property remains a detailed listing and links to its project through development_id.
When a unit is no longer available, it is archived from active search while remaining publicly visible inside the development as unavailable. Projects retain useful inventory context instead of showing only the units that happen to be on sale today.
Projects with multiple blocks stay simple: each block is represented as its own development, identified in its id, name, or both.
Version 2 models owners, branches, and agents without duplicating their contact data across every listing. The public contact priority is explicit:
The same model works for both individual listings and developments, while each keeps independent contact assignments.
Pagination is not required. Consumers can download a complete XML snapshot to temporary storage, stream listings with bounded memory, create worker batches, and compare deterministic fingerprints before processing changes.
Publishers can regenerate one stable feed URL in a background job every hour or more frequently. Atomic publication prevents consumers from ever reading a partially generated feed.
The data model and processing guidance are documented together so portals, CRMs, agencies, developers, and other companies can implement the same contract without reproducing RERA's internal systems.
Ready to build? Read the complete specification or start from the full XML example.
Need help? Contact the RERA technical team at it@rera.cy.
