NYC 311 Scraper: Service Requests by Type & Borough avatar

NYC 311 Scraper: Service Requests by Type & Borough

Pricing

Pay per usage

Go to Apify Store
NYC 311 Scraper: Service Requests by Type & Borough

NYC 311 Scraper: Service Requests by Type & Borough

Pull NYC 311 service requests by complaint type and borough via NYC Open Data: agency, descriptor, status and location. No login, no proxy, no browser.

Pricing

Pay per usage

Rating

0.0

(0)

Developer

Naimur Hasan

Naimur Hasan

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Categories

Share

NYC 311 Scraper

Pulls NYC 311 service requests by complaint type and borough through NYC Open Data. No login, no proxy, no browser.

Input

FieldTypeNotes
complaintTypestringExact type, e.g. Noise - Residential. Omit for all types.
boroughstringany | MANHATTAN | BROOKLYN | QUEENS | BRONX | STATEN ISLAND. Default any.
maxItemsintegerCap on requests, newest first. Default 100.

Output

One row per request: uniqueKey, createdDate, closedDate, agency, agencyName, complaintType, descriptor, status, borough, incidentZip, incidentAddress, city, latitude, longitude, resolutionDescription.

Notes

  • Filters are built as a SoQL $where clause, and single quotes in the value are escaped — without that, a complaint type like Children's Camp would break the query outright.
  • complaintType is an exact match, not a substring. NYC's vocabulary is specific: Noise - Residential and Noise - Street/Sidewalk are different types.
  • Coordinates come back as strings and are frequently absent for requests logged without a precise location; they are converted to numbers or left null.
  • The dataset is one of the largest open civic datasets in the world and is updated daily, so $order=created_date DESC plus maxItems is what keeps a run bounded.