# Seattle Crime Data Scraper (`acquistion-automation/seattle-crime-data-scraper`) Actor

Collects Seattle Police Department incident reports from the city's open-data portal. Returns each incident as a flat row with date, offense, precinct, and coordinates. Filter by precinct or NIBRS crime category.

- **URL**: https://apify.com/acquistion-automation/seattle-crime-data-scraper.md
- **Developed by:** [Acquisition Automation Co.](https://apify.com/acquistion-automation) (community)
- **Categories:** Other, News, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $19.00 / 1,000 results

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

![Acquisition Automation Co. Search less. Close more.](https://api.apify.com/v2/key-value-stores/AOdPHdOpeDpzEPS5f/records/banner.jpg)

## 🚓 Seattle Crime Data Scraper

> **Seattle Police Department incident reports as flat rows, with offense, NIBRS classification, precinct, beat, neighborhood, block address and coordinates.** Filter by precinct or crime against category, cap the run, export to CSV, Excel, JSON or XML. No API key and no registration.

Seattle publishes every SPD offense report to its open data portal, back to 2008. The portal is built for browsing, not for attaching to a diligence file. This Actor pulls the records you ask for and writes each offense into a dataset you can filter by neighborhood, by beat or by the block the business sits on.

| Who uses it | What they use the reports for |
|---|---|
| 🏪 Buyers of Seattle storefronts and service businesses | Checking what has been reported around an address before agreeing a price or a lease |
| 📋 Insurance and risk analysts | Counting property offenses by beat rather than by impression |
| 🏢 Commercial landlords and property managers | Comparing precincts and neighborhoods with the same set of columns |
| 📰 Journalists and civic researchers | Building a dated incident set with NIBRS categories attached |

### 📋 What it does

> 💡 **Why it matters:** a retail or service business is bought at a specific corner. The city's own offense record is the cheapest way to see what happens on that corner, and it is public.

- 🗺 **Filters by SPD precinct**, for example `WEST` or `NORTH`.
- 🏷 **Filters by NIBRS crime against category**: `PERSON`, `PROPERTY`, `SOCIETY` or `NOT_A_CRIME`.
- 📍 **Returns coordinates and the block address** where the city publishes them, plus beat, sector, neighborhood and reporting area.
- 🧾 **Keeps the report and offense identifiers**, so one report with several offenses stays traceable.
- ⏱ **Carries both timestamps**: when the offense happened and when it was reported.
- 💾 **Exports to CSV, Excel, JSON or XML**, from the run page or the API.

### 📊 Output

Every offense is one flat row. One report can produce several rows, one per offense. `REDACTED` is what the city itself publishes when it withholds a location, and `-` is its blank marker.

| Field | Type | Description |
|---|---|---|
| 🚔 `offense` | string | Offense name, for example `Simple Assault` |
| 🏷 `offense_category` | string | Broad category, for example `VIOLENT CRIME` or `ALL OTHER` |
| 🗂 `offense_sub_category` | string | Sub category, for example `ASSAULT OFFENSES` |
| ⚖️ `nibrs_crime_against_category` | string | NIBRS crime against category: `PERSON`, `PROPERTY`, `SOCIETY`, `ANY` or `NOT_A_CRIME` |
| 🔤 `nibrs_group_a_b` | string | NIBRS reporting group, `A` or `B` |
| 🔫 `shooting_type_group` | string | Shooting classification where one applies, `-` when it does not |
| 🧾 `report_number` | string | SPD report number, for example `2026-273587` |
| 🆔 `id` | string | Row identifier, the same value as `report_number` |
| 🆔 `offense_id` | string | Identifier for the individual offense inside the report |
| 📅 `offense_date` | string | When the offense occurred, local time |
| 🕓 `report_date_time` | string | When the report was filed, local time |
| 📍 `block_address` | string | Block level address, for example `48XX BLOCK OF SAND POINT WAY NE`. `REDACTED` on withheld locations |
| 🧭 `latitude` | number | Latitude in decimal degrees. `null` on withheld locations |
| 🧭 `longitude` | number | Longitude in decimal degrees. `null` on withheld locations |
| 🚓 `precinct` | string | SPD precinct, for example `North` |
| 🗺 `sector` | string | SPD sector letter |
| 📌 `beat` | string | SPD beat, for example `L2` |
| 🏘 `neighborhood` | string | Neighborhood name, for example `NORTHGATE`, or `-` where none is published |
| 🔢 `reporting_area` | string | Reporting area code. `REDACTED` on withheld locations |
| 📝 `title` | string | Repeats the offense name |
| 🔗 `url` | string | Link to the city's SPD crime dataset page |
| 🔗 `sourceUrl` | string | The same dataset page, kept for traceability |
| 🖼 `imageUrl` | string | Image field carried by the Actor template. `null` on every row |
| 🕒 `scrapedAt` | string | ISO timestamp of collection |
| ⚠️ `error` | string | `null` on a normal row |

#### Example rows

```json
{
  "imageUrl": null,
  "title": "All Other Offenses",
  "url": "https://data.seattle.gov/Public-Safety/SPD-Crime-Data-2008-Present/tazs-3rd5",
  "id": "2026-273587",
  "report_number": "2026-273587",
  "report_date_time": "2026-09-13T22:48:11.000",
  "offense_id": "73116934051",
  "offense_date": "2026-09-13T21:27:00.000",
  "nibrs_group_a_b": "B",
  "nibrs_crime_against_category": "ANY",
  "offense_sub_category": "ALL OTHER",
  "shooting_type_group": "-",
  "block_address": "REDACTED",
  "latitude": null,
  "longitude": null,
  "beat": "L2",
  "precinct": "North",
  "sector": "L",
  "neighborhood": "NORTHGATE",
  "reporting_area": "REDACTED",
  "offense_category": "ALL OTHER",
  "offense": "All Other Offenses",
  "sourceUrl": "https://data.seattle.gov/Public-Safety/SPD-Crime-Data-2008-Present/tazs-3rd5",
  "scrapedAt": "2026-09-14T16:38:05.377Z",
  "error": null
}
```

```json
{
  "imageUrl": null,
  "title": "Simple Assault",
  "url": "https://data.seattle.gov/Public-Safety/SPD-Crime-Data-2008-Present/tazs-3rd5",
  "id": "2026-273587",
  "report_number": "2026-273587",
  "report_date_time": "2026-09-13T22:48:11.000",
  "offense_id": "73116915953",
  "offense_date": "2026-09-13T21:27:00.000",
  "nibrs_group_a_b": "A",
  "nibrs_crime_against_category": "PERSON",
  "offense_sub_category": "ASSAULT OFFENSES",
  "shooting_type_group": "-",
  "block_address": "REDACTED",
  "latitude": null,
  "longitude": null,
  "beat": "L2",
  "precinct": "North",
  "sector": "L",
  "neighborhood": "-",
  "reporting_area": "REDACTED",
  "offense_category": "ALL OTHER",
  "offense": "Simple Assault",
  "sourceUrl": "https://data.seattle.gov/Public-Safety/SPD-Crime-Data-2008-Present/tazs-3rd5",
  "scrapedAt": "2026-09-14T16:38:05.473Z",
  "error": null
}
```

### ✨ Why choose this Actor

| | What you get |
|---|---|
| **The city's own record** | Rows come from Seattle's open data portal, not from a crime map app. |
| **No credentials** | The portal is public. No key, no account, no quota. |
| **25 fields, every run** | Same columns each time, so several precincts stack into one table. |
| **Offense level detail** | A report with three offenses gives three rows, each with its own NIBRS classification. |
| **You pay per row** | No subscription. A filtered run costs what it returns. |

### 🚀 How to use it

1. [Create a free Apify account](https://console.apify.com/sign-up). New accounts start with $5 of credit.
2. Open the Actor and select **Try for free**.
3. Set `precinct`, `category`, or neither for everything.
4. Set `maxItems` to cap the run.
5. Select **Start**, then export from the **Dataset** tab as CSV, Excel, JSON or XML.

A first run:

```json
{
  "maxItems": 10
}
```

Property offenses in the West precinct:

```json
{
  "precinct": "WEST",
  "category": "PROPERTY",
  "maxItems": 500
}
```

### ⚙️ Input

| Field | Required | Description |
|---|---|---|
| `precinct` | No | SPD precinct to filter on, for example `WEST`, `NORTH`. Empty returns every precinct |
| `category` | No | NIBRS crime against category: `PERSON`, `PROPERTY`, `SOCIETY` or `NOT_A_CRIME` |
| `maxItems` | No | How many incidents to collect per run. Default 10 |

### 💰 Pricing

Pay per result. No subscription, and no Apify platform usage on top.

| Apify plan | Free | Bronze | Silver | Gold | Platinum | Diamond |
|---|---|---|---|---|---|---|
| Per incident row | $0.021 | $0.0203 | $0.0197 | $0.019 | $0.019 | $0.019 |

| Rows collected | Cost on the Free plan |
|---|---|
| 100 | $2.10 |
| 1,000 | $21.00 |
| 10,000 | $210.00 |

**Free plan runs** return up to 10 rows as a preview. Any paid Apify plan lifts that to 1,000,000 per run.

### 🔌 Integrate with any app

The dataset is available through the Apify API as soon as the run finishes. Use `run-sync-get-dataset-items` for a one-shot call, webhooks to trigger what happens next, or the Make, Zapier, Airbyte and LangChain integrations listed on the Actor page.

### 🤖 Use with an AI agent

Give an agent live access to the incident record over the Model Context Protocol:

```bash
claude mcp add --transport http apify "https://mcp.apify.com?tools=acquistion-automation/seattle-crime-data-scraper"
```

Then ask it in plain language what was reported in a precinct and have it read the result back.

### ❓ Frequently asked questions

**Why do some rows say `REDACTED` and have no coordinates?**
Seattle withholds the location on certain reports, such as those involving sensitive offenses. The Actor returns the record as published, so `block_address` and `reporting_area` read `REDACTED` and the coordinates are `null`. Most rows carry a block address and a latitude and longitude.

**Why do two rows share one report number?**
One report can list several offenses. Each offense gets its own row and its own `offense_id`, while `report_number` stays the same.

**How do I look at one address?**
Filter by `precinct` or `beat`, then match on `block_address`, which is published at block level, or compute distance from `latitude` and `longitude`.

**What is the NIBRS crime against category?**
The federal classification of who or what the offense was against: a person, property or society. `category` in the input filters on it.

**Are `title`, `url` and `imageUrl` useful?**
Not for analysis. `title` repeats the offense, `url` repeats `sourceUrl`, and `imageUrl` is `null` on every row. They are kept so the schema stays stable between runs.

**What can I export?**
CSV, Excel, JSON and XML from the run page, or JSON straight from the API.

### 🔗 More from Acquisition Automation Co.

- [NIFC Wildfire Incidents Scraper](https://apify.com/acquistion-automation/nifc-wildfire-incidents-scraper)
- [SAM.gov Contract Opportunities Scraper](https://apify.com/acquistion-automation/sam-gov-contracts-scraper)
- [PublicSurplus Scraper](https://apify.com/acquistion-automation/publicsurplus-scraper)
- [IRS Exempt Organizations Scraper](https://apify.com/acquistion-automation/irs-eo-master-file-scraper)
- [BizBuySell Scraper](https://apify.com/acquistion-automation/bizbuysell-scraper)

### About Acquisition Automation Co.

We build automation for people buying businesses. The repetitive part of an acquisition search, checking listings, pulling public records, tracking owners and assets, is work a machine should do, so the buyer's time goes into judging deals instead of collecting them.

We add new Actors regularly. If there is a source you need and do not see here, tell us.

### 🆘 Support

Open an issue in the **Issues** tab of this Actor with your run ID, the input you used, and what you expected to get back.

### ⚠️ Disclaimer

This Actor is independent and is not affiliated with, endorsed by, or sponsored by the City of Seattle or the Seattle Police Department. It collects only publicly available data. Police reports describe allegations, not convictions. You are responsible for using that data in compliance with the source's terms of service and applicable law.

# Actor input Schema

## `maxItems` (type: `integer`):

How many incidents to collect per run.

## `precinct` (type: `string`):

Filter by SPD precinct (e.g. WEST, NORTH).

## `category` (type: `string`):

Filter by NIBRS crime-against category (PERSON, PROPERTY, SOCIETY).

## Actor input object example

```json
{
  "maxItems": 10
}
```

# Actor output Schema

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

Scraped Seattle PD Crime records

# 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 = {
    "maxItems": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("acquistion-automation/seattle-crime-data-scraper").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 = { "maxItems": 10 }

# Run the Actor and wait for it to finish
run = client.actor("acquistion-automation/seattle-crime-data-scraper").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 '{
  "maxItems": 10
}' |
apify call acquistion-automation/seattle-crime-data-scraper --silent --output-dataset

```

## MCP server setup

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

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/IkGNz7f0InqlHj66t/builds/kPhicuYzRaZ9m5kK4/openapi.json