Lisense logoLisense.
Log in

Florida brokerage recruiting data

Most brokerages recruit off stale lists and word of mouth — while the state publishes exactly who got licensed and who moved, every single week. Lisense diffs the official DBPR bulk extracts weekly and turns them into a change feed: new licenses, brokerage moves, status flips, rank changes, county moves, and churn. Filtered by county.

Who moved brokerages this week

The highest-signal recruiting list there is: agents who just changed brokerages in your county.

curl "https://api.lisense.dev/api/v1/changes?feed=movers&county=St.%20Lucie" \
  -H "Authorization: Bearer fl_live_..."

Who just got licensed

New licensees are new agents choosing a brokerage for the first time. Same feed, different event.

curl "https://api.lisense.dev/api/v1/changes?event=new&county=St.%20Lucie" \
  -H "Authorization: Bearer fl_live_..."

Pull a brokerage's whole roster

Once you spot movement, pull the full roster under an employer's license number to see who's there now.

curl "https://api.lisense.dev/api/v1/related/CQ1003371" \
  -H "Authorization: Bearer fl_live_..."

How the feed works

  • Weekly cadence. One event row per license per ingest; field-level old/new pairs ride along in the changes object.
  • Weeks start Monday. Pass a Monday YYYY-MM-DD as week, or omit it for the latest week.
  • CSV export. Add format=csv to drop the feed straight into a spreadsheet or CRM import.
  • Honest timestamps. Every event carries the snapshot date it was observed in — up to about a week of staleness, stated up front.

Ask in plain English instead

Connect Lisense to Claude once and skip the API calls: “Find me 50 agents licensed last week in St. Lucie County.” Setup takes two minutes.

Next steps