Developers

Integrate your CRM feed

Send your listings to Century 21 Global in REAXML. Test the exact mapping production uses — right here, before you go live.

One pipeline, two front doors

Push to the REST API or drop REAXML via SFTP — both funnel through the same validate → canonical-map → queue path.

Test = production

The validator below runs the identical mapping logic as live ingestion, so a passing dry-run means a working integration.

Quarantine, never drop

Malformed or invalid listings are reported with precise issues and quarantined upstream — never silently lost.

Test your integration

Paste a REAXML <propertyList> or a RESO Web API record and validate it — both map into the same canonical model. Neither format carries a currency, so a 3-letter ISO-4217 code is required.

Currency*CountrySource locale

<?xml version="1.0" encoding="UTF-8"?>
<propertyList>
  <residential modTime="2026-06-20-09:00:00" status="current">
    <agentID>OFFICE-001</agentID>
    <uniqueID>R12345</uniqueID>
    <listingAgent id="1">
      <name>Jamie Rivera</name>
      <telephone type="mobile">0400 111 222</telephone>
      <email>jamie@example-realty.com</email>
    </listingAgent>
    <price display="yes">980000</price>
    <address display="yes">
      <streetNumber>14</streetNumber>
      <street>Marine Parade</street>
      <suburb>Coogee</suburb>
      <state>NSW</state>
      <postcode>2034</postcode>
    </address>
    <category name="House"/>
    <headline>Sun-drenched family home near the beach</headline>
    <description>A bright four-bedroom home with ocean glimpses and off-street parking.</description>
    <features><bedrooms>4</bedrooms><bathrooms>2</bathrooms><garages>1</garages></features>
    <landDetails><area unit="squareMeter">420</area></landDetails>
    <objects><img id="m" url="https://example.com/photos/r12345-1.jpg" format="jpg"/></objects>
  </residential>
</propertyList>

Both formats map into the one canonical model via the same validate path — nothing is persisted.

The canonical preview + any issues appear here.

API reference

Per-office API-key auth (replaces REAXML's plaintext credentials). Full interactive docs: Swagger UI · OpenAPI spec

Method	Endpoint	Purpose
POST	`/v1/validate`	Sandbox dry-run — preview the canonical mapping + issues. No persistence, no auth.
POST	`/v1/feeds`	Validate + persist a feed (REAXML or RESO); returns per-listing actions. Requires your feed key (Authorization: Bearer).
GET	`/v1/listings/{office}/{uniqueId}`	Read a listing back as the platform stores it — confirm the mapping round-trips.

REAXML → canonical mapping

REAXML is adapter #1, not the schema. Every feed normalizes into the canonical superset:

REAXML reality	Canonical model
No currency in REAXML	Explicit currency code on every price (injected from office/country context).
AU-centric address, no lat/long	Country-first address + geocoded lat/long.
uniqueID unique per office	Composite identity key (sourceOfficeId + uniqueID).
No deleted status	Soft-delete state machine (status transitions + full-feed reconcile under the circuit breaker).
beds/baths in <features>, area varies	Normalized bedrooms/bathrooms + area in m².
Images url= or file=, ordered m,a,b…	Media order + hero flag preserved; photos served from the feed's own image URLs.