GM Road Casualty Accidents (Full STATS19 data)

Open data API in a single place

Provided by Transport for Greater Manchester

Get early access to GM Road Casualty Accidents (Full STATS19 data) API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
Created
Available languages
English
Keywords
Quality scoring

Dataset description

Full standard STATS19 fields data on reported road accidents in Greater Manchester. Please bear in mind that our STATS19 data (police data on road accidents is in a standardised national format) is a relational database, it consists of accident, vehicle and casualty records. The underlying structure of the data is essentially hierarchical. For each accident there is a single accident record, followed by a variable number of vehicle records and a variable number of casualty records. Casualty records are linked to vehicle records either because the vehicle struck the casualty or because the casualty was a driver or a passenger in a vehicle. In Greater Manchester, different councils have different viewpoints on which terminology should be used. However, it has been decided that at a Greater Manchester level, the term road accident should be used. This is the term that most members of the public would use and is also the one used by the Department for Transport on the national form used for the collection of the data. This data will be refreshed annually. A key to the codes used in the data can be found in the STATS19 road accident injury statistics - report form which is provided in the supporting information below. Please acknowledge the source of this information using the following attribution statement: Contains Transport for Greater Manchester data. Contains OS data © Crown copyright and database right 2024.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks