What does the New York City NY 311 data include?

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

Do I need an account with New York City NY 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 changed later, for example when it is 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.

New York City NY 311

Public data

Ready to useNo account needed

All service requests made to New York City's 311 line, 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.

22.4 millionservice requests as of September 2026
About 75,000new service requests a week
1 tableone row per service request

What people use it for

See which problems are most commonCount requests by complaint type to see what residents report most.
Compare boroughs and districtsBreak requests down by borough, community board or council district.
See which agency handles whatSee which city agency is responsible for each type of request.
See how residents report issuesCompare requests made by phone, app or other channels.

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 changed later, for example when it is closed, keeps the values it had when first loaded.

How it works

Choose New York City NY 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 New York City NY 311 data include?: One table, service requests, with one row per service request.
Do I need an account with New York City NY 311?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can New York City NY 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 changed later, for example when it is 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 cityofnewyork_311, version 0.1.0, a REST source, status stable, authentication none.

Vendor documentation: https://data.cityofnewyork.us/resource/erm2-nwe9.json

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`records` New York City 311 service request records.	stable	watermark	merge	`unique_key`	backfill_days

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 New York City NY 311 data into your warehouse

Last updated 2026-10-16.