Integrate your CRM feed

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.

Demo data & sample feeds

Grab a working sample of each inbound format — every file validates cleanly against the console above and can be POSTed as-is. The live read API also serves demo content you can extract while you build: the same endpoints your integration will verify against.

# 60-second quickstart: validate every sample + check your key's office scope
for f in reaxml-feed.xml reso-feed.json project-feed.json quickstart.sh; do
  curl -sO "https://c21global.cservices.au/samples/$f"; done
API_BASE=https://api.cservices.au C21_KEY=c21_yourkey bash quickstart.sh

# Verify a key by hand (401 = wrong/revoked; 200 lists the offices it may push for)
curl "https://api.cservices.au/v1/feeds/whoami" -H "Authorization: Bearer c21_yourkey"

# Extract demo data from the live read API (no auth) — listings, projects, directory
curl "https://api.cservices.au/v1/listings?country=AU&limit=5"
curl "https://api.cservices.au/v1/projects?stage=offThePlan"
curl "https://api.cservices.au/v1/projects/Century%2021%20Coastal/AU-PRJ-9001"   # project + child listings
curl "https://api.cservices.au/v1/countries"

# Dry-run a downloaded sample against the sandbox (no auth, persists nothing)
curl -X POST "https://api.cservices.au/v1/validate" -H "content-type: application/json" -d @project-feed.json

Prefer Postman? Import the ready-made collection — postman-collection.json — every request above plus push, full-snapshot, and admin examples, with {{baseUrl}} and {{clientKey}} variables.

Ready-made clients

Single-file, dependency-free clients for the whole API surface — drop one into your codebase and go. The MCP server plugs the API straight into an AI coding assistant as callable tools.

Get an API key

Reads and the validator need no key. To push, request one here — it's created instantly (shown once, scoped to your offices) and activates on operator approval. No email thread required: your integration can poll GET /v1/feeds/whoami to see the moment it goes live.

Build it with AI

The whole integration contract — endpoints, auth, all three payload formats, idempotency and snapshot semantics, error model, worked examples — lives in one self-contained document written for AI assistants: ai-integration-guide.md. Give it to Claude, ChatGPT, Copilot or Cursor with a prompt like:

Using the attached Century 21 Global integration guide, build a service that syncs
listings from our CRM to Century 21 Global:
- our CRM is <name it> and exports <describe your export format / API>
- validate every export against POST /v1/validate until it is clean
- push changes incrementally, plus a daily mode=full snapshot per office
- include our new-development projects via the project format, linked to their unit listings
- add a round-trip test that pushes a fixture and reads it back

API reference

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

REAXML → canonical mapping

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