Baltimore 311

governmentbuilt on requestauth: None

Sync Baltimore 311 service requests into your warehouse.

The Baltimore 311 connector syncs Baltimore service requests into analytics-ready tables in your data warehouse. Pull customer service requests with request type, intake method, status, due and close dates, agency and outcome from the Open Baltimore current-year 311 feature service, with Ingest handling pagination and retries so the tables stay current.

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

  • Service requests
  • Request status and outcome
  • Request types
  • Neighborhood and council district

Authentication

None. The Baltimore 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