Road risk data API
Every dataset behind our maps and league tables, published as stable JSON endpoints: collisions for every local authority district, vehicle crime by town, real-world car safety, MOT pass rates and workplace injuries. Free to use with attribution.
Seven endpoints, one base URL
All endpoints are static JSON over HTTPS at https://swiftassistuk.co.uk. No authentication, no SDK — a GET request returns the full dataset. Each response wraps its payload in a meta object (source, licence, generated date) and a data object. Start with the catalogue and go from there.
| Method | Endpoint | What you get | Data through |
|---|---|---|---|
| GET | /api/v1/index.json | The catalogue: every endpoint with its freshness, source and licence. | Live |
| GET | /api/v1/accidents-areas.json | Collision summaries for 125 tracked towns and cities: severity counts, five-year trends, latest and persistent hotspots, and pedestrian/cyclist/motorcyclist breakdowns. | 2025 |
| GET | /api/v1/accidents-districts.json | Every ONS local-authority district in Great Britain: collisions, casualties, KSI (killed or seriously injured), five-year trend and road-user modes. | 2025 |
| GET | /api/v1/vehicle-crime.json | Monthly street-level vehicle crime around tracked town centres, with the worst streets named. | June 2026 |
| GET | /api/v1/vehicle-safety.json | Real-world occupant outcomes for 129 car models over five years, banded A–D. | 2025 |
| GET | /api/v1/mot.json | MOT pass rates for 341 models, aggregated from DVSA anonymised test results. | 2023 |
| GET | /api/v1/workplace-injuries.json | HSE RIDDOR workplace injuries by industry, accident kind and region. | 2024/25 |
Try it now
# The catalogue — every endpoint, freshness and licence
curl -s https://swiftassistuk.co.uk/api/v1/index.json | jq '.data.endpoints[].path'
# Worst districts by killed-or-seriously-injured, latest year
curl -s https://swiftassistuk.co.uk/api/v1/accidents-districts.json \
| jq '.data.districts | sort_by(-.ksi) | .[:10] | .[] | {name, ons_code, ksi}'Free today. Bigger plans on the way.
Everything above is live and free under fair use — we ask only for attribution and a link. Professional and Business tiers are launching soon; register interest and we’ll write back when they open.
Free / Community
£0forever
- •Every endpoint listed above — full data, no cut-down version
- •No API key, no rate-limit gymnastics (fair use)
- •Attribution + a link to swiftassistuk.co.uk required
- •Refreshed automatically when official sources publish
Live now — no sign-up needed
Professional
£149/month
- •Commercial use without public attribution
- •Historic snapshots and change feeds
- •Postcode- and coordinate-level query endpoints
- •Email support with a named contact
Business
£499/month
- •Resale and white-label rights for the datasets
- •Custom aggregations and bespoke geographies
- •CSV/Parquet bulk exports and delivery to your bucket
- •Priority support and an uptime commitment
The small print, in plain English
Attribution. The underlying records are official open data; our aggregations are free to reuse if you credit us. Include this line (or equivalent) wherever the data appears: “Contains public sector information licensed under the Open Government Licence v3.0. Source attribution: swiftassistuk.co.uk” — with a link to this site where the medium allows.
Crime locations are approximate. police.uk anonymises street-level crime to snap points — a nearby point on or close to the street, not the exact address. Treat vehicle-crime coordinates as street-level, never property-level.
Scotland and vehicle crime. Police Scotland does not publish street-level data to police.uk, so Scottish towns are absent from the vehicle-crime endpoint. Collision data (DfT STATS19) covers all of Great Britain.
Not for resale. You may not resell these endpoints or repackage them as a competing data product without a commercial licence — email us and we’ll sort one out.
Provenance. Sources are DfT road casualty statistics (STATS19), data.police.uk, DVSA anonymised MOT results and HSE RIDDOR tables. Pipelines run automatically in the open — every number is traceable to an official release, and each response’s meta.generated date tells you when it was last rebuilt.
Been in an accident? Let's sort it.
One call starts your claim. Our line is open 24/7, 365 days a year.