docs / connectors / boston_311

Boston 311

governmentbuilt on requestauth: None

Sync Boston 311 service requests into your warehouse.

The Boston 311 connector syncs Boston service requests into analytics-ready tables in your data warehouse. Pull service requests and the service list, with status, description, timestamps and geocoded location from the Boston Open311 GeoReport v2 API, with Ingest handling pagination and retries so the tables stay current.

Boston 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 Boston 311 data in your warehouse or lake, each as its own table on the schedule you pick:

  • Service requests
  • Request status
  • Service list
  • Location and media

Authentication

None. The Boston 311 API is public and needs no credential. Reads on the Open311 GeoReport v2 endpoint are open; only submitting a new request needs an API key.

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