Real estate licenses,
one API across every state.
A normalized REST API for U.S. broker, salesperson, and brokerage records. We pull from official state regulators, map their fields into one consistent schema, and keep it refreshed — so your verification, onboarding, and compliance workflows stop breaking when state portals change.
// 50 live jurisdictions · 4.56M licensee records · source-aligned refresh
Prefer a tailored plan or procurement-friendly terms? Request access
raw → normalized
Interactive coverage map
See where records are live today
Live states and territories are shaded by active licensee records. The panel starts with network-wide totals; click a region to pin that jurisdiction's counts and refresh cadence.
Loading coverage map...
Public does not mean easy to use.
Real estate licenses are technically public records, but operationally fragmented. Every regulator publishes differently — different formats, different status vocabularies, different update schedules, different definitions of the same field.
Most teams do not want to spend engineering time sourcing every jurisdiction, reconciling column names, tracking source URL changes, and rebuilding pipelines every time a regulator updates its site.
We do that work upstream. You get a single normalized REST API with a clear path from each official source to a stable response shape.
- 50 jurisdictions, 50 license export formats
- Status codes that do not agree across regulators
- Lookup portals built for one license at a time
- Brokerage affiliations buried in PDFs and FOIA replies
- CSVs that arrive in three encodings on the same day
- Source URLs that change without notice
- One normalized JSON schema across every live jurisdiction
- Consistent status, license_type, expiration_date fields
- Batch verify — up to 100 licenses per request, mixed states
- Affiliation and supervisor relationships where the source carries them
- Source-aligned refresh with a last_verified timestamp on every record
- Stable REST API. We absorb upstream changes.
What Teams Tell Us
Common pain points we designed for
Signals from teams evaluating RELD for production workflows.
"We need one reliable API instead of training staff on 50 different state lookup sites."
Compliance Operations
"Our onboarding flow breaks when state portals change. We want a stable integration layer."
Proptech Product Team
"Having all license data in one place saves our team hours every week."
Brokerage Risk Team
Stop manually checking state portals.
Real estate license verification shouldn’t require visiting 50+ different websites with 50 different interfaces. We normalize it into one source — designed for software, not for one-off web lookups.
Comprehensive License Data
Real estate license records covering multiple U.S. states and territories, normalized and searchable.
Normalized Schema
Every state's data is mapped to a common structure. One integration handles all jurisdictions.
API-First Access
RESTful API designed for automation. Search, verify, and pull licensee data programmatically.
Compliance-Ready
Designed for license verification, compliance checks, and audit workflows out of the box.
Source-Aligned Refresh
Nightly for CA, TX, NY, CO, DE, AZ, CT, FL, IL, MI, SD, OH, MO; weekly for PA, AK, MA, VT, ND, WY, NJ, VA, PR, OR, WV, ME, RI, UT, KY, IA, MS, TN, MN, MD, WI, NM, LA, OK, AR, NH, NE, ID, IN; monthly source files for GA, HI, NV, KS, AL, NC, SC, MT. Every record carries a last_verified timestamp.
Growing Coverage
50 live jurisdictions (49 states plus 1 territory) with about 4.56M licensee records, including about 2.5M active records. More states shipping regularly.
Broker data
Built for broker and brokerage searches
Teams searching for real estate broker data need more than a name lookup. RELD gives them normalized fields they can use in onboarding, compliance, and product workflows.
Broker verification
Check whether a broker, associate broker, salesperson, or real estate business record appears active before onboarding, routing referrals, or approving access to a workflow.
Brokerage roster checks
Sync your CRM or spreadsheet, then verify every agent's state and license number in batches of up to 100 — Texas, California, Florida, and other live jurisdictions in a single API call.
Supervising-broker relationships
Use affiliation, supervisor, and affiliate endpoints in jurisdictions where RELD has relationship data to understand which supervising broker or brokerage is connected to a licensee.
How It Works
From state sources to your stack
We handle the collection and normalization so you can focus on building.
We gather the data
We collect real estate license records across U.S. states and territories so you don't have to.
We normalize everything
Every state's data gets mapped into a consistent, well-documented schema. One format, every jurisdiction.
You sign up and query the API
Create an account, generate an API key from the dashboard, then search licensees, verify status, and integrate into your workflows.
Clean API, structured data.
Query by state, name, license number, or status. Get back normalized JSON with consistent field names across every jurisdiction. One integration covers every live state and territory.
- RESTful JSON API
- Search by name, license number, state, or status
- Timestamps and metadata on every record
- Batch roster verify — up to 100 licenses per request, mixed states
GET /api/v1/licensees?state=CA&name=smith&status=active
Authorization: Bearer your_api_key
{
"data": [
{
"id": "a1b2c3d4-5678-4ef0-9abc-def012345678",
"full_name": "Jane Smith",
"license_number": "02104591",
"license_type": "Salesperson",
"status": "Active",
"state": "CA",
"expiration_date": "2027-03-15",
"brokerage": "Pacific Realty Group",
"last_verified": "2026-04-26T04:00:00Z",
"first_name": "Jane",
"last_name": "Smith",
"business_name": null,
"city": "Los Angeles"
}
],
"meta": {
"total": 47,
"page": 1,
"per_page": 25
}
}Why RELD
Data you can build on
Structured, searchable license data across U.S. jurisdictions — ready for your workflows.
Continuously Updated
Data is refreshed on a nightly, weekly, or monthly source-aligned cadence depending on the jurisdiction. Every record carries a timestamp.
Broad Coverage
Multiple U.S. states and territories live today, with more being added based on customer demand.
Normalized Structure
Every record follows a consistent schema regardless of which state it originated from.
Built for Production
Designed for compliance, verification, and analytics workflows. API-first, structured, and reliable.
Comparison
Why not just use state lookup portals?
You could check each state's website one at a time. Here's why teams choose a unified data layer instead.
| State Portals | RELD | |
|---|---|---|
| Data format | Different per state | Normalized JSON |
| Access method | Manual web lookup | REST API |
| Multi-state roster verify | Check each state portal separately | One POST, up to 100 licenses, mixed states |
| Automation | Not supported | Built-in |
| Data freshness | Unknown | Timestamped |
What teams ask before they integrate.
Short answers on coverage, sources, refresh cadence, real-time verification, and how to get an API key. Long-form details live on the Coverage and API docs pages.
Which states and territories are live today?
50 jurisdictions are live today: California, Texas, New York, Pennsylvania, Colorado, Delaware, Arizona, Alaska, Connecticut, Florida, Georgia, Hawaii, Illinois, Michigan, Massachusetts, Vermont, South Dakota, North Dakota, Ohio, Wyoming, New Jersey, Virginia, Puerto Rico, Oregon, Nevada, West Virginia, Maine, Rhode Island, Utah, Kansas, Kentucky, Iowa, Mississippi, Tennessee, Missouri, Alabama, Minnesota, Maryland, North Carolina, Wisconsin, New Mexico, Louisiana, Oklahoma, Arkansas, New Hampshire, Nebraska, Idaho, Indiana, South Carolina, and Montana — about 4.56M licensee records combined, including about 2.5M active records. The roadmap lists the other 1 U.S. states. The Coverage page breaks down each live jurisdiction's refresh cadence and record counts. Because of how the Hawaii and Georgia state regulators license their data, Georgia monthly-update coverage and Hawaii are available at an additional fee for now. Contact us for add-on pricing.
Where does the data come from?
From U.S. state and territory regulatory records. We collect, normalize, and keep it current so you can access it through a single API.
How fresh is the data?
CA, TX, NY, CO, DE, AZ, CT, FL, IL, MI, SD, OH, MO refresh nightly. PA, AK, MA, VT, ND, WY, NJ, VA, PR, OR, WV, ME, RI, UT, KY, IA, MS, TN, MN, MD, WI, NM, LA, OK, AR, NH, NE, ID, IN refresh weekly. GA, HI, NV, KS, AL, NC, SC, MT follow monthly source files that we check weekly for newly published data. Every record carries a last_verified timestamp and the GET /api/v1/coverage endpoint reports each source's most recent ingest time.
How do I get an API key?
Sign up through the dashboard to create an account, then generate your first API key there. If you need a custom plan, procurement-friendly terms, or higher limits, use the contact form and we will help.
Can I verify a specific license in real time?
Yes for live states and territories. Verify one license with GET /api/v1/licensees/verify, or POST up to 100 { state, license_number } pairs in a single batch request — mixed states allowed. Each result includes a verified flag and the full licensee record on a hit. Data reflects our most recent source-aligned refresh.
Is this a replacement for checking state portals?
For most operational workflows, yes — you query one normalized API instead of dozens of state websites. For regulatory filings or legal attestation, you should still reference the regulator directly.
Ready to simplify license data?
Create an account to get your API key, review plans, or contact us for custom coverage.