UK Crime Data by Postcode - Street-Level Reports & Trends

Turn any list of UK postcodes (or lat/lng points) into area crime intelligence - straight from the official UK Police API (data.police.uk). Each location gets every individual street-level crime within a ~1-mile radius plus a ready-made summary record: total crimes, breakdown by category, top category, and month-over-month trend.

No API key, no login, no scraping - this runs on the free official Police data service.

Who uses this data

• Property firms & due diligence - crime profile for any address before a purchase, letting decision, or development appraisal. Batch a whole portfolio of postcodes in one run.
• Relocation & lettings services - "how safe is this area?" answered with official numbers, not vibes. Drop the summary straight into client reports.
• Security companies - rank sales territories by burglary, vehicle crime, or robbery counts; pitch prospects with their own street's data.
• Insurers & risk models - structured category counts and trends per location, ready to join onto your book.
• Journalists & researchers - verifiable, citable official figures per neighbourhood, with month-over-month movement.

What you get

Per-crime records (recordType: "crime"):

Field	Example
location	M1 1AD (your input label)
category	burglary
month	2026-05
streetName	On or near Shopping Area
latitude / longitude	53.4796, -2.2367
outcomeStatus	Investigation complete; no suspect identified
persistentId	64-char stable crime ID

Per-location summary records (recordType: "summary") - the headline product:

Field	Example
totalCrimes	1893
byCategory	{ "violent-crime": 412, "shoplifting": 300, ... }
topCategory	violent-crime
crimesPerMonth	[{ "month": "2026-03", "count": 1720 }, ...]
momChange / momChangePct / trend	+112 / +6.3% / up

Use the Summaries dataset view for the per-location rollups and the Crimes view for the raw incidents.

How to use

1. Add postcodes and/or lat,lng pairs to Locations - one per area you care about. Bad postcodes are skipped with a warning, never crash the run.
2. Set Months of data: 1 for a snapshot of the latest month, 3+ for trend analysis (month-over-month change is computed automatically).
3. Optionally restrict Crime categories (burglary only, vehicle crime only, etc.). Empty = all crime.
4. Schedule it monthly to keep a rolling crime feed for your patch.

Set your expectations: the data lags ~1-2 months

Police forces publish street-level data on a delay - in mid-July, the newest available month is typically May. This is a property of the official dataset, not this actor. The actor detects the latest published month automatically and counts back from there, so you always get the freshest data that exists. Crime locations are also anonymised to the nearest map point ("On or near ...") by the police, so coordinates identify streets, not exact addresses.

One known coverage gap: Greater Manchester Police has not supplied full crime data to data.police.uk for several years, so Manchester-area locations return very low counts. All other England, Wales, and Northern Ireland forces publish normally (Scotland is not covered by this dataset).

Export & integrations

Results land in an Apify dataset - export CSV, Excel, JSON, or connect Google Sheets, Make, Zapier, Slack, and webhooks via Apify integrations.

Data source & licence

Data comes from the UK Police API (data.police.uk), covering England, Wales, and Northern Ireland, and is available under the Open Government Licence v3.0. Postcode geocoding via postcodes.io. This actor is not affiliated with the Home Office or any police force.

---

Need something more custom? Custom-drawn area polygons instead of a 1-mile radius, crime data joined to property listings, per-force outcome deep-dives, stop-and-search data, or a fully managed monitoring pipeline - message me via my Apify profile and I'll build it.