Cambridge MA 311
Public data
All service requests made through Cambridge, Massachusetts's Commonwealth Connect 311 service, as the city publishes them. Ingest delivers this data to a data warehouse you own as one table, and updates it on the schedule you choose. There is no code to write and nothing to install.
- 153,258service requests as of September 2026
- About 510new service requests a week
- 1 tableone row per service request
What people use it for
- See which problems are growingCount requests by type, week by week, to spot what is rising.
- Track how requests change over timeSee when each request was created and last updated.
- Map where requests come fromPlot requests using their coordinates to see where they cluster.
What you get
| Table | Each row is |
|---|---|
Service requestsservice_requests | One service request |
Good to know
Each run picks up requests created or changed since the last run, so changes show up after the next run.
How it works
- Choose Cambridge MA 311. The data is public, so there is nothing to sign in to.
- Pick where it goes. BigQuery, Snowflake, Databricks, Redshift and 10 more, in an account you own.
- Pick a schedule. Daily is the default, and weekly and monthly are there too.
- Ingest runs it from then on. If a run fails, your dashboard shows which table and why.
Questions
- What does the Cambridge MA 311 data include?
- One table, service requests, with one row per service request.
- Do I need an account with Cambridge MA 311?
- No. The data is public, so there is nothing to sign up for and nothing to paste in.
- Which warehouses can Cambridge MA 311 data go to?
- Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
- How fresh is the data?
- As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 15 minutes are on the Enterprise plan. Each run picks up requests created or changed since the last run, so changes show up after the next run.
- Will running it again create duplicate rows?
- No. Each row is stored once, by its key: when a run reads a row that is already there, it replaces that copy instead of adding a second one.
- Do I need to write code?
- No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.
For your data team: technical reference
Connector cambridge_311, version 0.1.0, a REST source, status beta, authentication none.
Vendor documentation: https://data.cambridgema.gov/resource/2z9k-mv9g.json
Configuration
No configuration required.
Resources
| Resource | Status | Plan | Write | Primary key | Overrides |
|---|---|---|---|---|---|
service_requestsCambridge MA Commonwealth Connect (311) service request records. | beta | watermark | merge | ticket_id | backfill_days |
Where this lands, and what else connects
Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.
Other sources Ingest connects for government teams: Abilene TX 311, Albany NY 311, Ann Arbor MI 311, Anne Arundel County MD 311, Auburn WA 311, Aurora IL 311.
- How Ingest reads a REST source
- Ingest for government teams
- The tables Ingest creates
- Every source Ingest connects
Get Cambridge MA 311 data into your warehouse
Last updated .