Do I need an account with San Jose CA 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 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.

San Jose CA 311

Public data

Ready to useNo account needed

San Jose CA 311 data, published as San Jose CA 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.

245,925rows as of September 2026
About 6,700new rows a week
1 tablein your warehouse

What you get

Table Each row is

Table	Each row is
records `records`	All 2026 San Jose 311 service requests from the city's CKAN datastore resource "2026 Service Requests" (daily refresh; the city publishes one resource per calendar year). Full re-read of the whole year on every run; Incident_ID is the city's incident id. The datastore stores every field as text, including the US-formatted "Date Created" and "Date Last Updated" columns, and they land as text. Column names are normalized by the engine (for example "Service Type" -> service_type).

records

records

All 2026 San Jose 311 service requests from the city's CKAN datastore resource "2026 Service Requests" (daily refresh; the city publishes one resource per calendar year). Full re-read of the whole year on every run; Incident_ID is the city's incident id. The datastore stores every field as text, including the US-formatted "Date Created" and "Date Last Updated" columns, and they land as text. Column names are normalized by the engine (for example "Service Type" -> service_type).

How it works

Choose San Jose CA 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 San Jose CA 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can San Jose CA 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 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 sanjoseca_311, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://data.sanjoseca.gov/dataset/311-service-request-data/resource/d886727c-60f1-4be7-9a30-f6806375b1a3

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`records` All 2026 San Jose 311 service requests from the city's CKAN datastore resource "2026 Service Requests" (daily refresh; the city publishes one resource per calendar year). Full re-read of the whole year on every run; Incident_ID is the city's incident id. The datastore stores every field as text, including the US-formatted "Date Created" and "Date Last Updated" columns, and they land as text. Column names are normalized by the engine (for example "Service Type" -> service_type).	beta	full	merge	`Incident_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, Auburn WA 311, Aurora IL 311.

Get San Jose CA 311 data into your warehouse

Last updated 2026-10-16.