Data Feeds is in early access. Contact us to set up
a subscription; the API and sync client described here open to early access
customers first.
Places
A place is a county, identified asus-<state>-<FIPS>, for example us-fl-12095 for Orange County, Florida. GET /v1/places lists the counties in your workspace’s coverage, with how many datasets each holds by topic.
Topics
Every dataset is filed under one topic from a fixed list, such aspermits, zoning, code_enforcement, planning, sales or parcels. GET /v1/topics returns the list. A subscription can name topics to receive only those.
Datasets
A dataset is one public record set from one source, such as Orange County’s building permits.keyColumnsare the columns that identify a record across versions. When a source has no stable key the list is empty, and records are matched by their content.refresh.cadenceis how often Ploti checks the source. A check that finds nothing new publishes no version;current.sourceCheckedAtstill moves.- Geometry is always WGS 84 (EPSG:4326).
Record ids
Every record has a_ploti_record_id, derived from the dataset and its key columns. It stays the same across versions for as long as the key columns do, so you can upsert and delete by it.
For a dataset without key columns, the id is derived from the record’s content: an edit at the source arrives as a delete of the old record and an upsert of the new one.
Envelope columns
Every snapshot and changes file carries these columns ahead of the dataset’s own:
Changes files add
_ploti_op (upsert or delete) and _ploti_change (added, changed or removed).
Because every dataset carries the same envelope, you can load many counties’ datasets side by side and ask “what changed in this county since Tuesday” without knowing any dataset’s columns.
Datasets you cannot subscribe to
Some data in the Ploti app is licensed from third parties rather than collected from public sources. It is available in the app and to agents, but not through Data Feeds, and does not appear inGET /v1/datasets.