Indianapolis 311

governmentbuilt on requestauth: None

Sync Indianapolis 311 service requests into your warehouse.

The Indianapolis 311 connector syncs Indianapolis service requests into analytics-ready tables in your data warehouse. Pull service requests, service names and activities, requested and closed timestamps, and status from the Mayor's Action Center service request feature layer on the Indy open data portal, with Ingest handling pagination and retries so the tables stay current.

Indianapolis 311 is not a certified connector yet. Ingest authors one from the vendor's API documentation when a customer asks for it, runs it against the real API, and only then lists it as deployable. Request it and it moves up the queue.

What you can sync

Ingest lands the following Indianapolis 311 data in your warehouse or lake, each as its own table on the schedule you pick:

  • Service requests
  • Request status and closure
  • Request types
  • Location and council district

Authentication

None. The Indianapolis 311 API is public and needs no credential.

Credentials go into a form, never into a chat, and are held in a secret store under your own path. Only the key NAMES ever reach the control database.

Resources