Data coverage

Public Florida county records — tax certificates and certificate-sale results published by each county tax collector and the LienHub, RealAuction, and TaxCertSale sale platforms, all already public for unrestricted re-use.

• County tax-collector certificate filesper-county tax-certificate, redemption & lands-available publications
• Certificate-sale platformsLienHub / RealAuction / TaxCertSale sale results & holder records

We are an independent platform. We do not republish anything that isn't already public, and we do not modify the underlying records — only normalize them.

• Daily workday imports pull every new certificate, sale result, and redemption each county tax collector and certificate-sale platform publishes.
• Periodic reconciliation re-imports the full certificate ledger, so status, holder, and redemption fields can't silently drift from the source of truth.

Daily imports verified by `daily_run` audit log.

Live operational health is published at /status — rendered from live database queries on every request.

Current production status: Live.

Counts below are read from the DatasetStatus singleton when this page is rendered — the same source consumed by /status and the homepage, so numbers can't drift between surfaces.

Records held vs. records read: we hold 10,522,109 queryable rows (certificates plus the parcels behind them), read from 30,474,078 source rows across every completed import. The read figure is higher because sources overlap and are deduplicated on write — it is not a count of records you can query.

Coverage period: tax certificates and certificate-sale results from each county tax collector that has been ingested. Not every county is ingested — see the per-county table below.

Redemption data, precisely: redemption status is carried on the certificate itself wherever the county published it, so certificates can be filtered by redeemed status today. A separate redemption event dataset (who redeemed, when, for how much) does not exist yet and there is no redemptions endpoint. The tile above counts the event dataset.

Every certificate includes: certificate number, county, parcel reference, tax year, status, face amount, interest / bid rate, and sale date. Populated where the source publishes it: owner of record, holder of record, and redemption / tax-deed status. Holder, redemption, and tax-deed records are not yet statewide datasets — the counts above are the whole of what we hold.

Certificate coverage depends on each county tax collector's certificate-sale publication and rolls out statewide across all 67 Florida counties. Coverage starts with the official county sale directory and expands into certificate-level data vendor-by-vendor. Every county is labeled so you always know what is in the dataset:

Access map.Each county's certificate sale runs through one of these channels. The count is how many of the 67 counties use it — LienHub is the largest but hardest to automate, so those counties begin directory-only and gain certificate detail through CSV / manual import and public-record requests.

Per-county coverage is tracked below, straight from the certificate rows we hold for each county.

Certificate-level data means individual certificate records are ingested and searchable for that county. Vendor tracked means we hold some records and the county is still being onboarded. Directory only means we hold the official sale directory (tax collector, sale URL, vendor) and no certificate records yet. 42 of 67 counties are at certificate level; 10 are partially ingested; 66 have a registered certificate-sale source.

• Normalized JSON via REST API at /api/v1.
• Raw source fields preserved on every certificate detail under certificate.raw — nothing is lossy.
• Downloadable CSV samples and a no-auth live API at /sample.
• OpenAPI 3.1 spec at /openapi.json for SDK generation and machine-readable docs.

Some fields are intentionally excluded; others are on the roadmap. Being explicit about both up front saves you a support ticket.

• Owner contact details

  Intentional PII gate. We surface the owner of record as it appears on the public tax roll, but do not attach phone, email, or mailing-address enrichment for individual owners.

• Email and phone

  Not in the source data. Anything you find elsewhere claiming to attach contact info to a parcel is enriched from a third-party source, not the county record itself.

• Parcel assessment & building detail

  Certificate records carry the parcel reference but not the full appraisal. For parcel-level value, owner history, and use code, cross-link to the property API at floridapropertyapi.com.

• Full historical certificate chains

  History depth varies by county tax collector. Today's API reflects the current certificate ledger plus the sale, redemption, and tax-deed events each county publishes.

• Public filing data only; not independently verified.
• Not for FCRA-covered decisions (credit, insurance underwriting, employment screening, tenant screening). See the FCRA notice for the full list.
• Sale dates reflect the certificate-sale date published by the county, not necessarily the date a holder recorded the lien.
• Status, total due, and redemption fields reflect the most recent tax-collector publication as of the last reconcile plus daily updates since.

Every field in our API response is traceable to the public record published by the relevant county tax collector or certificate-sale platform. Look up the certificate number or parcel ID on your county's official tax-collector / sale site and compare.

If you spot a discrepancy between our record and the county record, email support@fltaxcerts.com with the county and certificate number — we'll reconcile in the next daily run.