Coverage by jurisdiction

Real estate license API by state

See what's available for each U.S. state and territory. Where a jurisdiction is live, your team can verify licensees, look up brokers, search brokerage fields, and pull affiliation details through the RELD REST API today.

See overall coverage metrics, license lookup by state (50 with counts), or developer docs.

State lookup pages

How to use this directory

Each state page is a jurisdiction-specific landing page for the RELD API. Live pages describe the production status, available record counts, active-license counts, refresh cadence, and representative API calls for that jurisdiction. Roadmap pages explain that the state is not available in production yet and give teams a direct way to request prioritization.

RELD is built for programmatic real estate license workflows: broker onboarding, agent verification, brokerage roster checks, compliance reviews, referral network monitoring, and proptech data enrichment. The directory helps product and operations teams quickly answer whether a state can be queried today or whether it belongs in a coverage request.

For current totals across all live jurisdictions, use the coverage page. For public license lookup summaries with city-level counts (where source data includes cities), use the license lookup directory. For endpoint shapes, authentication, and example requests, use the developer overview. The state pages sit between those views: they keep jurisdiction-specific SEO and buying context close to the practical API details.

A production badge means the jurisdiction has passed ingestion and normalization work and is queryable through the API. It does not mean every regulator publishes the same fields. Some state sources provide rich brokerage and affiliation details, while others focus on individual license records and status data.

A roadmap badge means the jurisdiction is tracked but not yet part of live API coverage. Those pages are still useful for discovery because they explain the intended data product, keep the state visible to searchers, and give potential customers a clear path to tell us which missing jurisdiction affects a real implementation.

If you are comparing several markets, start with the production list, then open the individual state pages for the details that matter to your workflow. The same API can support different operational questions depending on whether you need a fast license-number verification, a broader name search, or evidence that a brokerage relationship was checked recently.

The directory also keeps internal planning simpler for teams evaluating a national rollout. Product managers can identify live states, compliance leads can spot missing markets, and developers can move from a state page into request examples without guessing whether a jurisdiction is actually available.

Production API

Live jurisdictions

51 state and territorial sources ingested today. Query programmatically via the API.

Backlog

On the roadmap

Need a state sooner? Coverage expansion is prioritized by demand — tell us what's blocking your rollout.

Request a state