Florida Vacation Rental License Evidence (DBPR Statewide)

Version 0.2 turns the statewide DBPR extract into an auditable evidence product: every record has a stable license key and fingerprint, each fetched district has a timestamp and content hash, and every run writes a hashed RUN-RECEIPT with its query, coverage, source set, failures, and dataset digest.

County, city, and name-filtered runs scan all seven DBPR district extracts even after the output limit is filled, because the same county can occur in multiple licensing districts. Unfiltered runs are explicitly labeled bounded_first_match; a limit is never presented as a complete statewide census. Partial source failures remain visible in the receipt and run status message.

Every state-licensed vacation rental in Florida — straight from the official registry, not scraped listings. Florida requires vacation rentals (whole units rented more than 3×/year for <30 days, or held out as such) to be licensed by the Department of Business & Professional Regulation (DBPR), Division of Hotels & Restaurants. This Actor returns that license registry: ~174,000 vacation rental licenses (Condos + Dwellings) statewide, filterable by county, city, status, license type, and name.

What you get (unified schema)

field	example
license_number	DWE1600123 / CND1600033
license_type	Vacation Rental - Condo or Vacation Rental - Dwelling
status	Current / Delinquent (+ status_code raw DBPR code)
name	business name (falls back to licensee name)
licensee_name	the licensed entity/person of record
address, city, county, state, zip	property (location) address, not mailing
expires	license expiry, ISO date
last_inspection	most recent DBPR inspection date (where present)
rental_units	number of rental units on the license
dbpr_district, source_url	which DBPR district extract the record came from
raw	the full original CSV row, verbatim

Nothing is invented: every field is carried verbatim from the DBPR extract (raw keeps the untouched source row). If DBPR doesn't publish a field, it's null.

Who uses this

• STR operators & property managers — verify "is this specific property state-licensed?" before signing, listing, or managing it.
• Compliance & enforcement vendors — join state licensure onto Airbnb/Vrbo listing data; Florida cities can't ban rentals but CAN require the state license.
• Property compliance teams & buyers — verify state-license status and expiry during diligence.
• Market analysts — county-by-county supply of licensed condo vs. dwelling rentals.

Input

{ "county": "Orange", "status": "current", "licenseType": "dwelling", "maxRecords": 200 }

All filters optional; empty input returns a 100-record statewide sample. Increase maxRecords for broader pulls. County/city matching is case- and punctuation-insensitive (st johns = St. Johns).

Source & honesty notes

• Source: DBPR Hotels & Restaurants "Lodging — Public Records" CSV extracts (hrlodge1.csv … hrlodge7.csv), the division's own published database of active lodging licenses. Public records, accessed logged-out, no login/API key. DBPR refreshes these extracts on its own cadence (files are current-license snapshots, not real-time).
• Statewide = all 7 district files. DBPR publishes by licensing-district office, and one county's records can appear in several district files — so this Actor always scans all 7 and filters, rather than guessing a county→district mapping.
• Status codes: DBPR does not publish a code dictionary on the extract page. Verified empirically at build time (2026-07-19) across all 174,596 vacation-rental rows: primary status 20 ⇔ expiry date in the future (matches DBPR's glossary term Current); 45 ⇔ expiry in the past (Delinquent — "has not completed a timely renewal"). Any other code is passed through verbatim as-is, never guessed. status_code always carries the raw value.
• Partial-failure behavior: if a district file fails to download after retries, the run continues with the remaining districts and flags a loud PARTIAL RESULTS warning in the log and run status — it never silently pretends to be statewide.
• One row per licensed location: DBPR issues group/collective vacation-rental licenses that can cover multiple properties, and the extract carries one row per property address — so the same license_number can legitimately appear on several records with different addresses. This is the source's own structure, preserved verbatim (dedupe on license_number + address if you need unique rows).
• Scope: state (DBPR) licenses only. City/county STR registration programs (e.g. Orlando, Miami Beach) are separate layers — see the STR Permit Registry actor for those.