Motor Vehicle Collisions - Crashes — NYC Open Data

NOTE: This dataset is temporarily not updating while its automated update process is being fixed. This fix is expected to be completed during the month of August. The Motor Vehicle Collisions crash table contains details on the crash event. Each row represents a crash event. The Motor Vehicle Collisions data tables contain information from all police reported motor vehicle collisions in NYC. This Actor returns it as one flat JSON row per record, with 34 declared fields — typed, named and documented in the dataset schema, so a spreadsheet or an agent can use it without guessing.

What you get

Field	Type	Meaning
number_of_pedestrians_injured	number	NUMBER OF PEDESTRIANS INJURED
number_of_pedestrians_killed	number	NUMBER OF PEDESTRIANS KILLED
contributing_factor_vehicle_2	string	CONTRIBUTING FACTOR VEHICLE 2
contributing_factor_vehicle_3	string	CONTRIBUTING FACTOR VEHICLE 3
collision_id	number	COLLISION_ID
number_of_cyclist_injured	number	NUMBER OF CYCLIST INJURED
number_of_cyclist_killed	number	NUMBER OF CYCLIST KILLED
cross_street_name	string	OFF STREET NAME
contributing_factor_vehicle_4	string	CONTRIBUTING FACTOR VEHICLE 4
location_city	string	LOCATION (city)
location_address	string	LOCATION (address)
number_of_persons_injured	number	NUMBER OF PERSONS INJURED
number_of_motorist_killed	number	NUMBER OF MOTORIST KILLED
vehicle_type_code1	string	VEHICLE TYPE CODE 1
number_of_persons_killed	number	NUMBER OF PERSONS KILLED
latitude	number	Latitude
longitude	number	Longitude
contributing_factor_vehicle_5	string	CONTRIBUTING FACTOR VEHICLE 5
off_street_name	string	CROSS STREET NAME
contributing_factor_vehicle_1	string	CONTRIBUTING FACTOR VEHICLE 1

The output schema lists all 34 fields; the table above is the first twenty.

Every row also carries sourceRowId, sourceUpdatedAt and scrapedAt, so a pipeline can tell one record from another and know exactly when it was read.

{
  "number_of_pedestrians_injured": 0,
  "number_of_pedestrians_killed": 0,
  "contributing_factor_vehicle_2": "Unspecified",
  "contributing_factor_vehicle_3": "Unspecified",
  "collision_id": 4455765,
  "number_of_cyclist_injured": 0,
  "number_of_cyclist_killed": 0,
  "cross_street_name": "text"
}

Inputs

Field	What it does
Filter (SoQL)	Applied at the source, so a narrow question fetches a narrow page instead of downloading everything.
Order	Empty keeps the publisher's own order; set a column to sort, for example amount DESC.
Maximum rows	Hard cap. The source is paged 1,000 rows at a time.
Time budget	Stops cleanly and reports how far it got.
Pause between pages	Keeps the run inside the publisher's rate limits.

Limitations

• This is one dataset, from one publisher. It is the Motor Vehicle Collisions - Crashes dataset as Police Department (NYPD) publishes it — not a national or cross-city equivalent, and not a merge with other sources.
• The publisher can change it. Columns are added, renamed and retired upstream; the field list here is the schema the Actor was generated from. A renamed column arrives as a new field only after the Actor is updated.
• Fields are typed from live records. A column that was empty in the sample is declared as text; a value that does not fit the declared type comes back null rather than being coerced into a wrong number.
• Records are what the publisher publishes. No geocoding, no de-duplication across datasets, no enrichment.
• Freshness is the publisher's. The data was last changed upstream on 2026-06-15. Where the publisher supplies a row timestamp it appears as sourceUpdatedAt; scrapedAt records when this Actor read the row.

Why this is different

• Motor Vehicle Collisions - Crashes — NYC Open Data declares all 34 of its output fields in the dataset schema, each with a type, a description and an example.
• The Actor reads the Motor Vehicle Collisions - Crashes dataset directly from NYC Open Data; no key, login or account is needed.
• Filters run at the source with SoQL, so a narrow request returns a narrow page rather than a full download.
• Every row is flat JSON: nested location objects become latitude and longitude, and no field holds a nested object.
• The row id is stable, so the same request de-duplicates instead of returning the same record twice.

FAQ

Do I need an API key? No. NYC Open Data publishes this dataset openly.

How fresh is it? The Actor reads the dataset live. scrapedAt records when each row was read, and sourceUpdatedAt carries the publisher's own row timestamp where it supplies one.

Can I filter by date or status? Yes — use the Filter field with SoQL, for example status = 'Active'.

What happens if my filter is wrong? The run stops with the portal's own message and the hint to check SoQL, rather than returning an empty dataset that looks like "no data".

Is this the whole dataset? Up to your row cap, paged 1,000 at a time. Raise the cap to read more.

What is sourceRowId? The publisher's own row id when it supplies one, otherwise a stable hash of the row. Either way it is what makes de-duplication and joins possible.

Pricing

Pay per result: $0.0005 per row. Each stored dataset row is billed, including any diagnostic row returned instead of results.

An Actor-start event is also charged at $0.0001 per GB of allocated memory (minimum one event), even if no rows are returned. At 1 GB or less, 1,000 result rows cost $0.5001 before any applicable Store discount.

Data source

NYC Open Data — Motor Vehicle Collisions - Crashes, published by Police Department (NYPD). Public data under the portal's open-data terms.