Florida Vacation Rental Licenses (DBPR Statewide) avatar

Florida Vacation Rental Licenses (DBPR Statewide)

Pricing

from $2.20 / 1,000 verified florida license records

Go to Apify Store
Florida Vacation Rental Licenses (DBPR Statewide)

Florida Vacation Rental Licenses (DBPR Statewide)

Every state-licensed Florida vacation rental (Condo + Dwelling) from the official DBPR public-records extracts - ~174k licenses. Filter by county, city, status, type, name.

Pricing

from $2.20 / 1,000 verified florida license records

Rating

0.0

(0)

Developer

Bryan

Bryan

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

18 days ago

Last modified

Share

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 preserves both the publisher's Last-Modified clock and our fetch time plus a 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)

fieldexample
license_numberDWE1600123 / CND1600033
license_typeVacation Rental - Condo or Vacation Rental - Dwelling
statusOfficial dictionary label when known; otherwise raw status_code
secondary_status, license_scopeSeparately mapped Active/Inactive and Single/Group/Collective; unknown values stay explicit
namebusiness name (falls back to licensee name)
licensee_namethe licensed entity/person of record
address, city, county, state, zipproperty (location) address, not mailing
expireslicense expiry, ISO date
last_inspectionmost recent DBPR inspection date (where present)
rental_unitsnumber of rental units on the license
dbpr_district, source_urlwhich DBPR district extract the record came from
source_updated_at, source_fetched_atpublisher update clock and our observation time
rawthe 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: the official lodging public-record layout supplies primary, secondary, and license-modifier dictionaries (accessed 2026-09-13; src/status-dictionary.js). Primary 20 is Current; 45 is Delinquent. Expiry remains a separate fact, never a status classifier. Unknown codes remain raw with a false status_known flag. The publisher notes legacy code 22 changed to 92; 92 remains unmapped pending an explicit entry.
  • 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.
  • License versus covered property: group/collective licenses may cover several properties; repeated license numbers and location/unit rows are preserved. rental_units is a published license count, not a list of independently matched dwellings. A license row alone does not prove membership of a customer-supplied unit; obtain separately cited covered-location evidence.
  • Completeness: RUN-RECEIPT.complete_for_filter requires all seven successful district scans and all matching rows returned. output_truncated is distinct from source success. A bounded sample, missing district or status-filtered result cannot establish a full negative.
  • 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.