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

Philadelphia PA 311

Public data

Ready to useNo account needed

Philadelphia PA 311 data, published as Philadelphia PA 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.

5.9 millionrows as of September 2026
About 8,600new rows a week
1 tablein your warehouse

What you get

Table Each row is

Table	Each row is
service_requests `service_requests`	Philadelphia 311 requests, read from the city's open-data copy (Carto SQL API table public_cases_fc, refreshed daily, roughly two days behind) in one-day windows of their requested_datetime, a single request per day, page size none. Records change after creation (status, updated_datetime, closed_datetime), so completed days are periodically re-read and merged on service_request_id; requests edited beyond the re-read horizon, and deletions from the published table, are not picked up. Older completed days wait longer between reads, becoming eligible again only after the longer of the refresh interval and a twentieth of their age at their last read (with the default interval, a day read at 280 days old waits 14 days).

service_requests

service_requests

Philadelphia 311 requests, read from the city's open-data copy (Carto SQL API table public_cases_fc, refreshed daily, roughly two days behind) in one-day windows of their requested_datetime, a single request per day, page size none. Records change after creation (status, updated_datetime, closed_datetime), so completed days are periodically re-read and merged on service_request_id; requests edited beyond the re-read horizon, and deletions from the published table, are not picked up. Older completed days wait longer between reads, becoming eligible again only after the longer of the refresh interval and a twentieth of their age at their last read (with the default interval, a day read at 280 days old waits 14 days).

How it works

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

Vendor documentation: https://opendataphilly.org/datasets/311-service-and-information-requests/

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`service_requests` Philadelphia 311 requests, read from the city's open-data copy (Carto SQL API table public_cases_fc, refreshed daily, roughly two days behind) in one-day windows of their requested_datetime, a single request per day, page size none. Records change after creation (status, updated_datetime, closed_datetime), so completed days are periodically re-read and merged on service_request_id; requests edited beyond the re-read horizon, and deletions from the published table, are not picked up. Older completed days wait longer between reads, becoming eligible again only after the longer of the refresh interval and a twentieth of their age at their last read (with the default interval, a day read at 280 days old waits 14 days).	beta	window	merge	`service_request_id`	lookback_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 Philadelphia PA 311 data into your warehouse

Last updated 2026-10-16.