# UK Police Crime Data: Street Crime, Stop & Search, Outcomes (`zaiqltd/uk-crime-data`) Actor

Street-level crimes with category, street, map point and latest outcome, plus stop and search records and neighbourhood policing priorities, from data.police.uk, the official UK police open data API. Search by GB postcode or coordinates and month; free counts by crime type per area.

- **URL**: https://apify.com/zaiqltd/uk-crime-data.md
- **Developed by:** [Zaiq](https://apify.com/zaiqltd) (community)
- **Categories:** Real estate, Business
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.80 / 1,000 police data records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## UK Police Crime Data: Street Crime, Stop & Search, Outcomes

Get **street-level crime, outcomes and stop and search records for any place in England, Wales and Northern Ireland** from **data.police.uk**, the official UK police open data API (published for the UK's police forces by the Single Online Home National Digital Team, under the Open Government Licence). Enter GB postcodes, outward codes such as `M1`, or latitude,longitude pairs and the months you want; each place is searched in the one-mile radius data.police.uk uses.

Every `crime` row gives the category (burglary, robbery, vehicle crime, violence and sexual offences and 10 more), the anonymised street and map point, and the latest police or court outcome. Add `stopAndSearch` rows (power used, object of search, outcome, age range, gender and ethnicity as published) and the `neighbourhood` policing team with its current priorities. Every place, month and data type also gets a **free summary that counts every record found** by crime type and outcome, even when you cap the paid rows.

No API key, login or proxy setup. Data covers the last 36 months; data.police.uk publishes each month about six to eight weeks after it ends.

Tested in Apify's cloud: the default input delivered 79 paid rows. The example below is a real delivered cloud row.

### What you get

| Field | What it holds |
|---|---|
| recordType | `crime`, `stopAndSearch` and `neighbourhood` are paid rows; `summary` is free. Filter on it before importing. |
| location, postcode, searchLatitude, searchLongitude | What you entered and the centre point used for the one-mile search. |
| force, forceName, neighbourhoodId | The police force and neighbourhood team covering the search point. |
| month | The YYYY-MM month the record was published for. |
| crimeId, persistentId | data.police.uk crime ID, and the 64-character ID that links a crime to its outcomes (empty for anti-social behaviour). |
| category, categoryName | Crime type code and label. |
| outcomeCategory, outcomeDate | Latest outcome (e.g. Under investigation, Awaiting court outcome, Offender given a caution) and its month. |
| outcomeHistory | With `includeOutcomeHistory`: every outcome the police and courts recorded for the crime, oldest first. |
| streetName, streetId, latitude, longitude | Anonymised location: data.police.uk snaps every record to a nearby map point and labels it On or near <street>. |
| searchType, dateTime, legislation, objectOfSearch, outcome | Stop and search: type, date and time, the power used, what was searched for, and the outcome. |
| gender, ageRange, selfDefinedEthnicity, officerDefinedEthnicity | Stop and search: published demographics of the search, exactly as the force reports them. |
| neighbourhoodName, description, teamWebsite, teamPhone, teamEmail, teamLinks, stations, priorities | The neighbourhood team: name, page, published team contacts, police stations and current priorities (issue, action, dates). Individual officers are never listed. |
| found, delivered, alreadyDelivered, byCategory, byOutcome, status, note | Free summary per place, month and data type: totals over every record found, plus why anything is empty, capped or failed. |
| sourceUrl, scrapedAt | The official data.police.uk request and the fetch time. |

### What people use it for

- **Property and relocation research:** compare crime by type around homes, offices or sites before buying, renting or investing; the free summary gives the full monthly count by crime type.
- **Insurance and risk scoring:** feed burglary, vehicle crime and robbery counts per postcode into pricing or underwriting models.
- **Retail and security planning:** benchmark shoplifting and theft around stores, car parks and shopping areas month by month.
- **Journalism and local news:** find what happened near a place, how many crimes were solved, and what outcomes courts reached.
- **Stop and search analysis:** study the powers used, outcomes and published demographics of stop and search by force and area.
- **AI agents and chat assistants:** answer questions such as how safe a street is, or what the local police team's priorities are, with official data.

### How to use it

1. Enter one or more places in **Postcodes or coordinates**: GB postcodes (SW1A 2AA), outward codes (M1) or latitude,longitude (53.4808,-2.2426). For Northern Ireland, use coordinates.
2. Leave **Months** empty for the latest month, or list up to 12 months as YYYY-MM.
3. Choose the **Data to fetch** (crimes, stop and search, neighbourhood team) and, optionally, crime types.
4. Set **Maximum records per place, month and data type** and a **Maximum cost per run** in Apify, then start the run.
5. Read the `crime`, `stopAndSearch` and `neighbourhood` rows, and the free `summary` rows for full counts and notes.

### Input

| Field | Example | Notes |
|---|---|---|
| locations | \["SW1A 2AA", "M1 1AE"] | 1-50 GB postcodes, outward codes or latitude,longitude pairs. Northern Ireland postcodes are refused (their lookup licence does not allow commercial use): enter coordinates. |
| months | \["2026-08", "2026-09"] | Up to 12 months; empty = the latest month published. |
| dataTypes | \["crimes", "stopAndSearch", "neighbourhood"] | Default: crimes. |
| crimeCategories | \["burglary", "robbery"] | Empty = every type. Summaries count only the chosen types. |
| maxRecordsPerLocation | 100 | Paid-row cap for each place, month and data type (1-10,000). Capped rows are taken evenly across crime types. |
| includeOutcomeHistory | false | One extra request per crime for its full outcome history. |

### Output

Each result is one row in the run's dataset (download it as JSON, CSV, Excel, XML or HTML, or read it through the API). An example row (values shortened):

```json
{
  "recordType": "crime",
  "resultId": "crime-137530066",
  "location": "SW1A 2AA",
  "postcode": "SW1A 2AA",
  "searchLatitude": 51.503541,
  "searchLongitude": -0.12767,
  "force": "metropolitan",
  "forceName": "Metropolitan Police Service",
  "neighbourhoodId": "E05013806N",
  "month": "2026-09",
  "crimeId": 137530066,
  "persistentId": null,
  "category": "anti-social-behaviour",
  "categoryName": "Anti-social behaviour",
  "outcomeCategory": null,
  "outcomeDate": null,
  "outcomeHistory": null,
  "context": null,
  "locationType": "Force",
  "locationSubtype": null,
  "searchType": null,
  "dateTime": null,
  "involvedPerson": null,
  "gender": null,
  "ageRange": null,
  "selfDefinedEthnicity": null,
  "officerDefinedEthnicity": null,
  "legislation": null,
  "objectOfSearch": null,
  "outcome": null,
  "outcomeLinkedToObjectOfSearch": null,
  "removalOfMoreThanOuterClothing": null,
  "operation": null,
  "operationName": null,
  "streetName": "On or near Terminus Place",
  "streetId": 1675983,
  "latitude": 51.496234,
  "longitude": -0.144433,
  "neighbourhoodName": null,
  "description": null,
  "population": null,
  "teamWebsite": null,
  "teamPhone": null,
  "teamEmail": null,
  "teamLinks": null,
  "stations": null,
  "priorities": null,
  "dataType": null,
  "status": null,
  "found": null,
  "delivered": null,
  "alreadyDelivered": null,
  "byCategory": null,
  "byOutcome": null,
  "note": null,
  "sourceUrl": "https://data.police.uk/api/crimes-street/all-crime?lat=51.503541&lng=-0.12767&date=2026-09",
  "scrapedAt": "2026-11-12T19:06:51Z"
}
```

Each place, month and data type also gets one free `summary` row: `found` is every record data.police.uk returned (after your crime-type filter), `delivered` the new paid rows and `alreadyDelivered` matches already written for another place in the run (overlapping areas are not charged twice). `byCategory` and `byOutcome` count every record found, so a capped run still shows the whole area: for example 3,556 crimes in the square mile around SW1A 2AA in September 2026, 727 of them other theft. A record named `SUMMARY` in the key-value store gives totals, request counts and the time taken.

### Pricing

- **$0.001 per record ($1 per 1,000 crimes, stop and search records or neighbourhood teams)**; $0.0009 on Silver and $0.0008 on Gold and higher plans, plus Apify's $0.00005 start.
- Summaries, records already delivered for another place in the same run, empty searches and failures are free.
- Cloud runs on 12 November 2026 charged exactly one event per delivered record.

What typical jobs cost at the list price:

| Job | Cost |
|---|---|
| Default: 100 crimes around SW1A 2AA for the latest month (free summary counts all 3,556) | $0.10 |
| Two places, one month, 20 crimes + 20 stop and search + team each (62 records) | $0.062 |
| 1,000 crimes | $1.00 |
| Full counts only: maxRecordsPerLocation 1 for 10 postcodes | $0.01 |

Set Maximum cost per run in Apify. A cloud test on 12 November 2026 stopped cleanly at two paid rows with a $0.00255 limit; free summaries are retained.

### Tips

- Need area statistics rather than every record? Set `maxRecordsPerLocation` to 1: the free summary still counts every crime by type and outcome.
- Busy city centres have thousands of crimes a month within a mile; a low cap keeps cost down while the summary keeps the totals.
- Use outward codes (e.g. `LS1`) for a district centre, or coordinates for exact points and for Northern Ireland.
- Months appear about six to eight weeks after they end; an unpublished month gets a free `not-published` summary with the published range.
- Some forces do not publish stop and search for every month; the summary says so instead of returning an empty list silently.

### Use it through the API

**Python**

```python
from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("zaiqltd/uk-crime-data").call(run_input={"locations": ["SW1A 2AA", "M1 1AE"], "dataTypes": ["crimes", "neighbourhood"], "maxRecordsPerLocation": 50})
for row in client.dataset(run.default_dataset_id).iterate_items():
    print(row)
```

**JavaScript**

```js
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('zaiqltd/uk-crime-data').call({"locations": ["SW1A 2AA", "M1 1AE"], "dataTypes": ["crimes", "neighbourhood"], "maxRecordsPerLocation": 50});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
```

**HTTP (one call, results back)**

```bash
curl -X POST 'https://api.apify.com/v2/acts/zaiqltd~uk-crime-data/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>' \
  -H 'Content-Type: application/json' \
  -d '{"locations": ["SW1A 2AA", "M1 1AE"], "dataTypes": ["crimes", "neighbourhood"], "maxRecordsPerLocation": 50}'
```

### Integrations and schedules

- **Schedules:** run it every hour, day or week from the Apify Console (Schedules) and keep a history of results.
- **Make, Zapier, n8n, Google Sheets, Slack, Airtable:** connect it through Apify's integrations, or send each finished run to a **webhook**.
- **Datasets:** results stay in the run's dataset; export them or read them by API whenever you need them.

### Use it with AI agents (MCP)

Add Apify's MCP server with this Actor already pinned (`https://mcp.apify.com?tools=zaiqltd/uk-crime-data`) to Claude, ChatGPT, Cursor, VS Code or any MCP client. The agent can find this Actor and run it for you: ask it for street-level crimes for the latest month around SW1A 2AA and M1 1AE, with the neighbourhood policing team and its priorities, up to 50 crimes per place; read the free summaries for full counts by crime type. AI agents can also pay for runs directly through Apify's agentic payments.

### Limits

- Locations are approximate by design: data.police.uk anonymises every record to a nearby map point and street label, and the one-mile radius is fixed by the API.
- Crime records carry the month, not the day. Stop and search records carry a date and time.
- Data comes from police forces as published; categories and outcomes are theirs, and forces sometimes revise past months.
- GB postcodes are turned into map points with postcodes.io (ONS and Ordnance Survey open data). Northern Ireland postcodes cannot be used commercially under that licence, so enter coordinates there.
- No officer names: the neighbourhood team row lists team contacts the force publishes and its priorities only.
- Only public, keyless endpoints are used, paced under the published rate limit (15 requests a second).

### FAQ

**Do I need a data.police.uk or police API key?**

No. data.police.uk is open and keyless; you only need your Apify account to run the Actor.

**Why is the street 'On or near ...' and the map point not the exact address?**

data.police.uk anonymises every record to protect victims: it snaps each one to the nearest of a set of anonymous map points. This Actor passes those points through unchanged.

**Can I get crime for a whole city?**

Enter several postcodes or coordinates across it. Overlapping areas are fine: a crime found by two places is delivered and charged once, and both summaries count it.

**Why do some crimes have no outcome?**

Anti-social behaviour has no outcome in the data, and recent crimes may not have one yet. Use `includeOutcomeHistory` to see every recorded outcome for crimes that have them.

**Is this data licensed for commercial use?**

data.police.uk publishes under the Open Government Licence v3.0, which allows commercial use with attribution: 'Contains public sector information licensed under the Open Government Licence v3.0.'

### Related Actors from Zaiq

- [property-listings](https://apify.com/zaiq/property-listings): property listings to pair with local crime counts
- [zillow-scraper](https://apify.com/zaiq/zillow-scraper): US homes, if you compare markets
- [company-registry-search](https://apify.com/zaiq/company-registry-search): official UK company records from Companies House and seven other registries

### Support

Questions, a site that changed, or a field you need? Open an issue on this Actor's **Issues** tab: we answer there, usually within a day.

***

Also found as: UK crime data, data.police.uk API, police.uk crime map data, crime by postcode UK, UK crime statistics, stop and search data, street-level crime, crime outcomes UK, neighbourhood policing priorities, England and Wales crime data.

# Actor input Schema

## `locations` (type: `array`):

1-50 places: GB postcodes (SW1A 2AA), outward codes (M1) or latitude,longitude (53.4808,-2.2426). Each is searched in the one-mile radius data.police.uk uses. Northern Ireland: use coordinates.

## `months` (type: `array`):

Up to 12 months, e.g. 2026-09. Leave empty for the latest month published. data.police.uk keeps the last 36 months and publishes each month about 6-8 weeks after it ends.

## `dataTypes` (type: `array`):

Crimes (street-level crimes and anti-social behaviour with the latest outcome), stop and search records, and the neighbourhood policing team with its current priorities.

## `crimeCategories` (type: `array`):

Only these crime types (crimes data only). Leave empty for every type. Free summaries count only the chosen types.

## `maxRecordsPerLocation` (type: `integer`):

A cap on paid rows for each place, month and data type (1-10000). The free summary still counts every record found. A busy city-centre square mile can have 2,000+ crimes a month.

## `includeOutcomeHistory` (type: `boolean`):

Adds every outcome the police and courts recorded for each crime (one extra request per crime, so slower). Off: the latest outcome only.

## Actor input object example

```json
{
  "locations": [
    "SW1A 2AA",
    "M1 1AE"
  ],
  "months": [],
  "dataTypes": [
    "crimes",
    "neighbourhood"
  ],
  "crimeCategories": [],
  "maxRecordsPerLocation": 50,
  "includeOutcomeHistory": false
}
```

# Actor output Schema

## `results` (type: `string`):

Dataset: the results.

## `summary` (type: `string`):

What each input returned, and notes.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "locations": [
        "SW1A 2AA",
        "M1 1AE"
    ],
    "months": [],
    "dataTypes": [
        "crimes",
        "neighbourhood"
    ],
    "maxRecordsPerLocation": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("zaiqltd/uk-crime-data").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "locations": [
        "SW1A 2AA",
        "M1 1AE",
    ],
    "months": [],
    "dataTypes": [
        "crimes",
        "neighbourhood",
    ],
    "maxRecordsPerLocation": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("zaiqltd/uk-crime-data").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "locations": [
    "SW1A 2AA",
    "M1 1AE"
  ],
  "months": [],
  "dataTypes": [
    "crimes",
    "neighbourhood"
  ],
  "maxRecordsPerLocation": 50
}' |
apify call zaiqltd/uk-crime-data --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,zaiqltd/uk-crime-data"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/sQlk02eeKNYTXOwSq/builds/MVGlRAZTxhaBBYlte/openapi.json
