SourceFinch Verified · Community associations & real estate
Florida condominium projects and associations: Central Florida West
Every approved or acknowledged condominium project in Florida's Central Florida West region from the DBPR Division of Florida Condominiums, Timeshares, and Mobile Homes file: project and file numbers, units, recorded date, status and the association (managing entity).
- Healthy · 100% of observed runs successful
- Community associations & real estate
- Florida Department of Business and Professional Regulation (DBPR)
- US-FL / Florida
- Publisher's public bulk file or feed
- 10 typed fields
Monitor this sourceAPI, CLI, SDK and MCP
What changed9 changes in 7 days, latest
At a glance
- Jurisdiction
- US-FL / Florida
- Publisher updates
- Refreshed weekly by DBPR
- Recommended schedule
- Weekly for your monitor; SourceFinch verifies the recipe weekly
- Records per run
- 9,355 in the latest run
- Record key
project_number- Acquired from
- Publisher's public bulk file or feed:
https://www2.myfloridalicense.com/sto/file_download/extracts/Condo_CW.csv - Recipe
- v1.0.0, approved October 3, 2026
- Version notes
- First Verified version: every project in the DBPR Central Florida West condominium file, typed units and recorded dates.
- Verified since
- October 3, 2026
- Last green run
- November 14, 2026
- Changes, last 7 days
- 9 · see what changed
What the data contains
Florida's Division of Florida Condominiums, Timeshares, and Mobile Homes (part of the Department of Business and Professional Regulation) records every condominium created under chapter 718, Florida Statutes, and the association that manages it. DBPR publishes the approved and acknowledged projects as weekly-refreshed CSV files by region; this source reads the Central Florida West file, covering Charlotte, Citrus, Collier, DeSoto, Glades, Hardee, Hendry, Hernando, Highlands, Hillsborough, Lee, Manatee, Pasco, Pinellas, Sarasota and Sumter counties (about 9,300 projects). Each weekly run reads the whole file and returns one record per condominium project: DBPR project number, file number, condominium name, county, number of units, the date the declaration was recorded, primary and secondary status (for example Approved and Delinquent), and the managing entity: the condominium association's DBPR number and name. A monitor reports new projects, status changes such as an association becoming delinquent on its annual fees, and associations that change. Street addresses of the project and of the managing entity are not read, so records never carry a mailing address (some associations are managed from an officer's home). Terminated, rejected or withdrawn projects are not in the file.
Fields and types
Every record has these fields. The key field project_number identifies a record across runs, so changes are reported field by field.
| Field | Type | Description |
|---|---|---|
project_numberkey | string | DBPR condominium project number (for example PR1G005497). The record key. |
file_number | string, nullable | DBPR file number of the project. |
name | string | Condominium name as filed. |
county | string, nullable | County of the condominium (DBPR spelling, for example Dade). |
units | integer, nullable | Number of units in the project. |
recorded | date, nullable | Date the declaration of condominium was recorded. |
primary_status | string, nullable | DBPR primary status, for example Approved or Acknowledged. |
secondary_status | string, nullable | DBPR secondary status, for example Current or Delinquent (annual fees). |
association_number | string, nullable | DBPR number of the managing entity (the condominium association). |
association_name | string, nullable | Name of the managing entity (the condominium association). |
Sample output
The first 5 of 9,355 records from SourceFinch's own run on November 14, 2026, exactly as delivered.
| Field | Record 1 | Record 2 | Record 3 | Record 4 | Record 5 |
|---|---|---|---|---|---|
project_number | PR1M003173 | PR1M003174 | PR1M003175 | PR1M001339 | PR1M001340 |
file_number | 47396 | 47397 | 47398 | 47083 | 47084 |
name | EAGLESWOOD I, A CONDO | EAGLESWOOD II, A CONDO | EAGLESWOOD III, A CONDO | POINTE ROYALE CONDO A | POINTE ROYALE CONDO B |
county | Pasco | Pasco | Pasco | Lee | Lee |
units | 36 | 12 | 8 | 47 | 47 |
recorded | 1984-02-03 | 1985-08-23 | 1986-10-14 | 1981-11-12 | 1984-08-23 |
primary_status | Approved | Approved | Approved | Approved | Approved |
secondary_status | Delinquent | Delinquent | Delinquent | Delinquent | Delinquent |
association_number | MA00010701 | MA00010701 | MA00010701 | MA00005225 | MA00005225 |
association_name | EAGLESWOOD CONDO ASSN INC | EAGLESWOOD CONDO ASSN INC | EAGLESWOOD CONDO ASSN INC | POINTE ROYALE CONDO ASSN INC | POINTE ROYALE CONDO ASSN INC |
Sample as JSON
[
{
"name": "EAGLESWOOD I, A CONDO",
"units": 36,
"county": "Pasco",
"recorded": "1984-02-03",
"file_number": "47396",
"primary_status": "Approved",
"project_number": "PR1M003173",
"association_name": "EAGLESWOOD CONDO ASSN INC",
"secondary_status": "Delinquent",
"association_number": "MA00010701"
},
{
"name": "EAGLESWOOD II, A CONDO",
"units": 12,
"county": "Pasco",
"recorded": "1985-08-23",
"file_number": "47397",
"primary_status": "Approved",
"project_number": "PR1M003174",
"association_name": "EAGLESWOOD CONDO ASSN INC",
"secondary_status": "Delinquent",
"association_number": "MA00010701"
},
{
"name": "EAGLESWOOD III, A CONDO",
"units": 8,
"county": "Pasco",
"recorded": "1986-10-14",
"file_number": "47398",
"primary_status": "Approved",
"project_number": "PR1M003175",
"association_name": "EAGLESWOOD CONDO ASSN INC",
"secondary_status": "Delinquent",
"association_number": "MA00010701"
},
{
"name": "POINTE ROYALE CONDO A",
"units": 47,
"county": "Lee",
"recorded": "1981-11-12",
"file_number": "47083",
"primary_status": "Approved",
"project_number": "PR1M001339",
"association_name": "POINTE ROYALE CONDO ASSN INC",
"secondary_status": "Delinquent",
"association_number": "MA00005225"
},
{
"name": "POINTE ROYALE CONDO B",
"units": 47,
"county": "Lee",
"recorded": "1984-08-23",
"file_number": "47084",
"primary_status": "Approved",
"project_number": "PR1M001340",
"association_name": "POINTE ROYALE CONDO ASSN INC",
"secondary_status": "Delinquent",
"association_number": "MA00005225"
}
]Evidence behind every value
- Each run keeps the publisher's exact response, hashed with SHA-256. This sample came from a response with hash
4251783cc2f28f8c5c219bfa73b4cb3cd16e74ca7a7ad07926ac22039864fdb9. - Every value records where it came from in that response: a CSS path into the retained capture.
- Each run gets a signed manifest (Ed25519) timestamped by an RFC 3161 authority: this run's manifest hash is
e26756cbecd847d86358f3a742303c61200cec86de00bcaf31cbbcef09d574e8, timestamped November 14, 2026. - The compliance state at capture is recorded with the evidence: robots.txt hash and verdict, AI-preference signals, crawler identity and the usage rights below.
- Download any run as an evidence bundle (WACZ) and check it offline, without trusting SourceFinch:
sourcefinch verify-bundle run.wacz.
Terms posture and usage rights
- Terms
- Automated access permitted · publisher's terms
- robots.txt
- Allows this path · SHA-256
8ac252e54dbb3730… - AI-preference signals
- None observed at review
- Public record
- Yes. Chapter 119, Florida Statutes (public records), and s. 718.501, F.S. (condominium filings with the Division of Florida Condominiums, Timeshares, and Mobile Homes).
- Reviewed
- October 3, 2026; next review April 3, 2027
- Licence basis
- Publisher's terms of use
- Commercial use
- Allowed
- Redistribution
- Allowed
- Attribution
- Required (text below)
The Florida Department of Business and Professional Regulation publishes its licensee and condominium files on a free download site to meet its public-records duty under chapter 119, Florida Statutes, as quote/comma-delimited ASCII text refreshed weekly. The site disclaimer offers no technical support and disclaims responsibility for damage from downloads; it places no restriction on reuse. robots.txt allows the extracts path. Florida public records may be inspected and copied by anyone (s. 119.01, F.S.).
Source: Florida Department of Business and Professional Regulation, Division of Florida Condominiums, Timeshares, and Mobile Homes, public records download.
Usage rights travel with every record SourceFinch delivers (API, exports, webhooks and evidence bundles). They are our documented understanding of the publisher's stated terms, not legal advice.
Reliability
- Runs, last 30 days
- 4
- Green
- 100%
- Failed
- 0
- Median run time
- 2.7 s
- Latest run
- success, November 14, 2026
Measured on completed runs of this recipe version across SourceFinch, anonymized, within a rolling 30-day window. First successful observation: October 3, 2026. A new recipe has only the history collected since that date; this is not a 30-day uptime guarantee.
Use it
Every surface creates the same monitor from this Verified recipe. Monitors keep record history, report field-level changes and deliver by webhook, export or email. You confirm you have the right to collect the source (rights: true).
Console
Open this recipe in the console: it preserves the reviewed URL, fields and record key. Review the latest captured sample, confirm source rights, and choose a schedule before creating your monitor.
Portable recipe
Copy into the console's Import or share a recipe panel to customize fields, types and schedules. This configuration contains no captured records or workspace IDs.
{
"schema": "sourcefinch/source@1",
"name": "Florida condominium projects and associations: Central Florida West",
"url": "https://www2.myfloridalicense.com/sto/file_download/extracts/Condo_CW.csv",
"recipe": {
"mode": "http",
"format": "csv",
"items": "*",
"fields": {
"name": "Condo Name",
"units": "Units",
"county": "County",
"recorded": "Recorded Date",
"file_number": "File Number",
"primary_status": "Primary Status",
"project_number": "Project Number",
"association_name": "Managing Entity Name",
"secondary_status": "Secondary Status",
"association_number": "Managing Entity Number"
},
"required": [
"project_number",
"name"
],
"csv": {
"delimiter": ",",
"header": true,
"encoding": "windows-1252"
},
"types": {
"recorded": "date",
"units": "integer"
}
},
"schedule": "weekly",
"key_field": "project_number"
}source.json
The request body used by the API, CLI and SDK examples.
{
"name": "Florida condominium projects and associations: Central Florida West",
"url": "https://www2.myfloridalicense.com/sto/file_download/extracts/Condo_CW.csv",
"recipe": {
"mode": "http",
"format": "csv",
"items": "*",
"fields": {
"name": "Condo Name",
"units": "Units",
"county": "County",
"recorded": "Recorded Date",
"file_number": "File Number",
"primary_status": "Primary Status",
"project_number": "Project Number",
"association_name": "Managing Entity Name",
"secondary_status": "Secondary Status",
"association_number": "Managing Entity Number"
},
"required": [
"project_number",
"name"
],
"csv": {
"delimiter": ",",
"header": true,
"encoding": "windows-1252"
},
"types": {
"units": "integer",
"recorded": "date"
}
},
"key_field": "project_number",
"schedule": "weekly",
"rights": true,
"catalog": {
"slug": "florida-condominium-projects-central-florida-west",
"version_id": "9381581b-0ebd-4912-8a8c-3606b1a1184c"
}
}REST API
Create an API key under Console → API keys. Reference: /docs/api.
# the Verified entry (fields, recipe, sample, terms) as JSON
curl https://sourcefinch.com/v1/catalog/florida-condominium-projects-central-florida-west -H "Authorization: Bearer $SOURCEFINCH_API_KEY"
# create the monitor from source.json (below)
curl -X POST https://sourcefinch.com/v1/sources \
-H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d @source.json
# then run it now (later runs follow the schedule)
curl -X POST https://sourcefinch.com/v1/sources/$SOURCE_ID/runs \
-H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
-H "Idempotency-Key: $(uuidgen)"CLI
The sourcefinch CLI is not on npm yet; see /docs/cli.
sourcefinch login
sourcefinch catalog get florida-condominium-projects-central-florida-west --source-json > source.json
sourcefinch sources create --file source.json
sourcefinch runs create $SOURCE_ID --wait
sourcefinch records $SOURCE_IDTypeScript SDK
The SDK is not on npm yet; see /docs/sdk.
import { SourceFinch } from "@sourcefinch/sdk";
const sf = new SourceFinch({ apiKey: process.env.SOURCEFINCH_API_KEY });
const entry = await sf.catalog.get("florida-condominium-projects-central-florida-west");
const source = await sf.sources.create({
catalog: { slug: entry.slug, version_id: entry.recipe.version_id },
name: entry.name.slice(0, 100),
url: entry.acquisition_path.endpoint,
recipe: entry.recipe.definition,
key_field: entry.recipe.key_field,
schedule: entry.recipe.schedule,
rights: true, // you confirm you have the right to collect this source
});
const run = await sf.runs.wait((await sf.runs.create(source.id)).id);
console.log(run.status);MCP
Remote MCP server with OAuth; see /docs/mcp.
claude mcp add --transport http sourcefinch https://sourcefinch.com/mcp
# then ask your agent:
"Use SourceFinch to monitor Florida condominium projects and associations: Central Florida West: get_catalog_source florida-condominium-projects-central-florida-west,
then create_source with its create_source_args (dry run first), then run_source."Pricing
Each check is one run, whatever the number of records, and failed runs are free. On its default weekly schedule this source uses about 4 runs a month, which fits the Free plan's 300 runs. It uses HTTP acquisition, so no browser runs are needed. See plans.
Related sources
More from Florida Department of Business and Professional Regulation (DBPR) and in community associations & real estate.
SourceFinch is independent and is not affiliated with or endorsed by Florida Department of Business and Professional Regulation (DBPR). This page describes florida condominium projects and associations: central florida west as SourceFinch acquires it.