What does the Seattle WA 311 data include?

One table, service requests, with one row per service request.

Do I need an account with Seattle WA 311?

No. The data is public, so there is nothing to sign up for and nothing to paste in.

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 adds requests created since the last run. A request that is updated later, for example when closed, keeps the values it had when first loaded.

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.

Seattle WA 311

Public data

Ready to useNo account needed

Seattle customer service requests with creation dates, coordinates, and zip codes. 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.

2.5 millionservice requests as of September 2026
About 6,900new service requests a week
1 tableone row per service request

What people use it for

Watch requests build over timeTrack creation dates to see when calls arrive and spot busy seasons.
Map geographic demandPlot coordinates and zip codes to find which neighborhoods call most.
Analyze request volumeCount requests by period to understand growth in specific problem areas.

What you get

Table	Each row is
Service requests `records`	One service request

Good to know

Each run adds requests created since the last run. A request that is updated later, for example when closed, keeps the values it had when first loaded.

How it works

Choose Seattle WA 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 Seattle WA 311 data include?: One table, service requests, with one row per service request.
Do I need an account with Seattle WA 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Seattle WA 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 adds requests created since the last run. A request that is updated later, for example when closed, keeps the values it had when first loaded.
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 seattle_311, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://data.seattle.gov/dataset/Customer-Service-Requests/5ngg-rpne

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`records` Seattle 311 customer service requests. Incremental sync follows creation time; later edits to previously loaded cases are not refreshed.	beta	watermark	merge	`servicerequestnumber`	backfill_days