COUNTY SOURCES. TRACEABLE JSON.
Twenty workflows.
Traceable county data.
Explore two phases of ten county workflows each. A parcel lookup joins direct county assessment and collector records, retrieves an available source PDF, and returns structured JSON with field provenance.
Implementation, hosted verification and live source outcomes are separate. County joins are checked by exact parcel/account identity. Annual-roll mode remains explicitly labelled; it does not establish current payment status.
Try a lookup
POST /api/v1/property/lookup
County coverage and API contract ↗
Request JSON
Collection happens when you submit. Source failures stay failures. No saved-data fallback or automatic switch from county sources to an annual roll.
API response
ReadySelect a county to see its coverage before sending a request.
Submit a parcel ID to see the actual API response.
Sources for the selected county
Explore all 67 Florida counties and their coverage
Office links come from the Florida Department of Revenue directory. A directory link is not a live scraper. “Annual roll” refers to a fresh query of the state-published annual dataset. Each county has a source-derived 2026 sample; current record availability can differ.
| County | Annual roll | County assessment | Tax collector | PDF parsing | Hosted verification |
|---|
Use the same endpoint in your application.
The public demonstration is limited to parcel lookups. Production authentication, quotas and batch jobs remain pilot work. County adapter activation requires exact parcel and field verification. Assessment, tax billing, payments and balances retain their source meaning and record years.