Skip to main content
Welcome to the Realie Property Data API. The v3 generation serves the same endpoints you already use, backed by our current national data build: fresher sales (through mid-May 2026 in most states), per-unit parcel identity via realieParcelId, corrected building characteristics, and nationally normalized assessor codes.
One dataset, two response shapes. All responses are served from the v3 data generation. The v3 shape — documented in this tab — is the full nested parcel record, matching bulk exports apart from delivery-specific fields (bulk records carry a per-load _id; API responses omit it), and is the default for new accounts. The v2-compatible shape is the flat field layout existing integrations already receive, served from the same v3 data through a compatibility layer; it is documented in the legacy tab and remains available with no sunset date announced. The shape is an account-level setting that every API key on the account inherits: existing accounts can enable the v3 shape from the dashboard’s Usage page, which is a one-way switch. Endpoint URLs, authentication, rate limits, and billing are identical for both.

​
Getting Started

1

Sign In

Create an account and sign in. Every account starts on the Free plan with a monthly token allowance shared across the Platform and API.
2

Enable API Access

Add a payment method from Billing to enable API requests. We place a temporary $0.50 authorization hold to verify the card, then release it immediately.
3

Copy Your API Key

Open Usage and select API access to copy your key. Once API access is enabled, send it on every REST request in the Authorization header (see Authentication below).
4

Explore our Endpoints

Discover the full range of property data available by exploring our endpoints, conveniently accessible via the sidebar on the left.

​
Authentication

Send your API key in the Authorization header on every REST request (property, premium, historical analytics, key administration, and usage endpoints).
The same key is also accepted with a Bearer prefix, which some HTTP clients add automatically. The scheme name is case-insensitive (Bearer, bearer, and so on):
Empty or malformed credentials, unsupported auth schemes, repeated Bearer prefixes, internal whitespace in the key, and comma-combined credentials still return 401.

​
Coming from v2?

Most integrations keep working unchanged: endpoint URLs, request parameters, and the large majority of response fields are identical. The differences that matter — a permanent parcel id (realieId), a handful of renamed or removed fields, decimal bathrooms, and new vocabularies for some coded fields — are catalogued in the v2 → v3 migration guide.