Do I need an account with Auburn 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.

Will running it again create duplicate rows?

No. Each run replaces the table, so it never holds two copies of the same row.

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.

Auburn WA 311

Public data

Ready to useNo account needed

Auburn WA 311 data, published as Auburn WA 311 publishes it. 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.

What you get

Table	Each row is
records `records`	All 'See, Click, Fix' citizen service requests submitted to the City of Auburn (WA). The publisher has not refreshed this dataset since 2025-03-25; each run re-fetches the full ~24.4k-row collection (~25 pages) ordered by requested_datetime + service_request_id, and replaces the destination table, so it always mirrors the published snapshot.

How it works

Choose Auburn 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

Do I need an account with Auburn WA 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Auburn 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.
Will running it again create duplicate rows?: No. Each run replaces the table, so it never holds two copies of the same row.
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 auburnwa_311, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://data.auburnwa.gov/d/bduj-5afh

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`records` All 'See, Click, Fix' citizen service requests submitted to the City of Auburn (WA). The publisher has not refreshed this dataset since 2025-03-25; each run re-fetches the full ~24.4k-row collection (~25 pages) ordered by requested_datetime + service_request_id, and replaces the destination table, so it always mirrors the published snapshot.	beta	full	replace	`service_request_id`	-

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, Aurora IL 311, Austin TX 311.

Get Auburn WA 311 data into your warehouse

Last updated 2026-10-16.