Skip to main content
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.
A subscription is the set of datasets you receive and where they go.

What a subscription covers

  • places: every dataset in each county, now and later. A dataset Ploti adds to one of them joins the subscription and sends dataset.added.
  • topics: only these topics within places. Every topic when left out.
  • datasetIds: datasets to include on their own, from any county in your coverage.
Places must be in your workspace’s coverage. Changing a subscription with PATCH sends dataset.added and dataset.removed for the datasets that join or leave.

Pull

With "delivery": { "type": "pull" }, you fetch files yourself with signed links from the manifest and from each version. Nothing is written anywhere on your side until you ask.

Push to your bucket

Ploti can write each version’s files into your own bucket as soon as they publish.
Create a role in your account that Ploti can assume, with s3:PutObject on the bucket and prefix, then:
Ploti writes this layout under your prefix:
manifest.json lists the version’s files with row counts and checksums. current.json names the latest version delivered, written last, so a reader that sees it can trust the files it names are complete. GET /v1/subscriptions/{id}/deliveries lists what was written, when, and any failures. Events are sent once a version is delivered, so dataset.updated means the files are already in your bucket.

Other destinations

Delivery is not limited to the options above. Every destination receives the same files (snapshots, changes, schemas and manifests), so adding one is a matter of writing them somewhere new. If you ingest into a warehouse, a database or another store, tell us and we will deliver there.

Formats