The open standard for
real estate development data
REOP, the Real Estate Open Protocol, is a free, open JSON standard for new-development property data. One versioned document connects developers, marketplaces, portals and AI agents.
The protocol, and a marketplace built on it
Two different things with one name. This site explains the protocol. The marketplace shows what it enables.
REOP, the Real Estate Open Protocol
An open specification for describing a developer, a project, its buildings, floors, unit types, units and availability as one JSON document. Vendor neutral, versioned, MIT licensed.
- Canonical JSON Schema and a generated OpenAPI document
- Published vocabularies for amenities, statuses, media roles and room conventions
- Validated examples, a migration guide per release and a machine-readable version index
- Anyone can produce or consume REOP documents; no account, no fee
The REOP marketplace
A working registry and marketplace built on the protocol: it ingests REOP documents, validates and upgrades them, serves every project back as a ProjectDocument, and shows verified developer data to buyers, search engines and AI agents.
- Reference API:
GET /v1/projects/{id}/reop, inventory updates, version manifest - Verified developer profiles, embeddable project widgets, AI sales agent
- One of the things you can build with REOP, not the protocol itself
Why an open protocol?
Property data lives in PDFs, spreadsheets and portal forms. REOP gives every system the same document to read and write.
One document, every channel
A project is described once, as a REOP document, and reused by every portal, broker site, campaign and integration. Update the source and every consumer sees the same facts.
Decoupled inventory
Unit types (marketing data) and specific units (live inventory) are separate. Publish a project before sales open, then stream availability and prices from the ERP or CRM as InventoryUpdate documents.
AI native
Consistent fields, controlled vocabularies and multilingual text let AI agents read, compare and recommend projects instead of guessing from marketing copy.
Provenance and trust
Every document names its producer and version. Registries can mark developer-verified data, so buyers, agents and search engines know what is official.
Multilingual, multi-currency
Every human text is a localized map, prices carry ISO 4217 currencies, and room counts follow documented market conventions, so the same document serves local and international audiences.
Versioned and extensible
Every document declares its protocol version. Minor releases only add; deprecated members stay valid until the next major; vendor data travels under extensions and is preserved by every intermediary.
Don't be invisible to the future
Discovery is moving from search boxes to conversations. If an AI agent cannot read a building's data, that building does not exist to the buyer asking.
A REOP document is the structured answer: unit types, prices, availability, amenities, legal facts and media, in a shape language models and marketplace bots can rely on.
Listen to the vision
Why REOP was created and what an open data layer changes for the industry. An AI-generated conversation produced with Google's NotebookLM.
Publish once. Stay current everywhere.
Describe each project in one REOP document: unit types, floor plans, prices, payment plan, amenities, legal status, media and 3D tours. Every portal, broker and campaign reads the same facts, and an update at the source propagates to all of them.
When sales open, the ERP or CRM keeps availability in sync with small InventoryUpdate deltas instead of manual edits on five portals.
Stop scraping. Consume a standard.
Instead of brittle scrapers and one-off feeds, read versioned JSON documents with a published schema. Unknown members are preserved by design, so a producer on a newer minor never breaks your pipeline.
Vocabularies give you the same amenity, status and media keys from every developer, in every language they publish.
Consumer checklist and the migration guide from 1.3.0
Lead the industry
Developers and platforms adopting REOP now shape how the standard grows, and are the first whose data is readable by the next generation of buyers' tools.
- Verified developer data on REOP-based marketplaces
- Structured, AI-readable project information
- Direct integration support
// GET https://api.reop.io/v1/projects/prj_rothschild_collection/reop (ProjectDocument, REOP 1.4.0) { "protocol": { "name": "REOP", "version": "1.4.0" }, "project": { "id": "prj_rothschild_collection", "name": { "en": "The Rothschild Collection", "he": "אוסף רוטשילד" }, "status": { "state": "underConstruction" }, "unitModels": [ { "id": "model_roth_1br", "specs": { "rooms": 2, "bedrooms": 1 }, "availability": "available" } ], "inventory": [ { "id": "u_roth_101", "status": "available", "links": { "modelId": "model_roth_1br" } } ] }, "developer": { "id": "dev_tlv_urban_01", "name": { "en": "Tel Aviv Urban Heights" } } }
Stop scraping. Start building.
Building an agent, a valuation model, an ERP connector or a 3D-tour integration? Consume a versioned, validated JSON document with a stable schema URL, and emit one when you have data to share.
Unit types carry rooms and bedrooms as independent facts, media and floor plans are typed objects, virtual tours are vendor-neutral experiences, and inventory links back to its unit type by id.
What's in REOP 1.4.0
A consolidation release: everything from the previous version stays valid, and the model gains the objects producers kept asking for.
- ProjectDocument and InventoryUpdateOne document per project for APIs, and a partial, idempotent availability delta for ERP and CRM sync, next to the catalog feed.
- Media as objectsGalleries, floor plans, documents and 3D or virtual-tour experiences share one vendor-neutral shape, with previews, roles and credited logos.
- Rooms and bedroomsTwo independent facts with documented market conventions, never derived from each other.
- Published vocabularies and extensionsAmenities, statuses, media roles, payment phases and more as labelled lists; vendor data under
extensions; any ISO 4217 currency.
Questions
What is REOP?
REOP (Real Estate Open Protocol) is a free, open JSON standard for new-development property data. It defines how a developer, a project, its buildings, floors, unit types, units and availability are described in one versioned document, so developer systems, marketplaces, portals and AI agents can exchange the same data without scraping or custom feeds.
Is REOP free to use?
Yes. The schema, OpenAPI document, vocabularies, examples and tools are published under the MIT license in the REOP-IO/reop-protocol repository. Anyone can produce or consume REOP documents.
Which version is current, and how do I validate a document?
REOP 1.4.0, released on 22 October 2026, is the current version. Every document declares protocol.version. The canonical JSON Schema is published at reop.io/schema/1.4.0/reop.schema.json and the release index at reop.io/schema/versions.json. The protocol repository ships a validator: node tools/validate.mjs your-document.json.
What is the difference between REOP and the REOP marketplace?
REOP is the protocol: an open specification anyone can implement. The REOP marketplace at app.reop.io is one implementation built on it: a registry that ingests, validates and serves REOP documents and shows what the standard enables. The protocol does not depend on the marketplace.
How do I publish a project or keep availability in sync?
Produce a ProjectDocument that validates against the current schema and send it to a REOP-compatible registry, for example PUT /v1/projects/{id} on the reference API. Unit status and price changes travel as an InventoryUpdate: a partial, idempotent delta from an ERP or CRM to POST /v1/projects/{id}/inventory/updates.
Build on an open standard
Read the specification, validate your first document, or see what a marketplace built on REOP looks like.