Loading...
What you can build
Read and write your own listings, leads, offers, and coordination artifacts. Validated, rate-limited, and safe to retry.
Signed, replay-safe delivery for listing lifecycle, offer transitions, showing scheduling, and lead handoff. Retried on transient failure.
Issue keys from your dashboard with least-privilege scopes. Rotate and revoke without a support ticket. Every request is attributed for audit.
Signed archive of what you have contributed — listings, leads, messages, credit ledger entries. Portable, timestamped, and verifiable.
A single ledger meters AI actions and higher-tier API use. Bundled monthly for eligible subscribers; overage available in one-time packs.
Buyer, seller, identity, and AML gates are enforced at the API layer. If a request is missing a prerequisite, you receive a structured, actionable error.
API design principles
Structured error codes with actionable next-step hints when a user needs to take action. No mystery failures — we fail closed and tell you why.
Mutating endpoints accept an idempotency key. Payments, listing publishes, and signature workflows are all safe to retry.
Public routes are versioned. Breaking changes ship as a new major version, never in place. Deprecation windows are announced in advance.
Everything you write via the API you can export via the API. No screen-scraping, no support ticket for a CSV. The connection layer is the product; your data is not.
How to get access
Full request/response contracts, endpoint documentation, and sandbox credentials are provided to approved partners under a mutual agreement. We do this on purpose: a real estate API touches personally identifiable information, licensed representation, and payment flows, and we want to know who is building on it.
If you are building a proptech product, an investor tool, a Web3 integration, or an internal system for a brokerage, we would like to talk.