# US Law Enforcement, Corrections & Public Safety Leads Scraper (`scrapesage/us-law-enforcement-leads`) Actor

Scrape every US law enforcement agency (police, sheriff, state, federal, tribal & campus), correctional facility, EMS station & 911/EOC: name, address, phone, type, staffing, capacity, NAICS, website, geo + lead score. Filter by category, state & size. Official HIFLD gov data + monitor mode.

- **URL**: https://apify.com/scrapesage/us-law-enforcement-leads.md
- **Developed by:** [Scrape Sage](https://apify.com/scrapesage) (community)
- **Categories:** Lead generation, Automation, Other
- **Stats:** 1 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.50 / 1,000 public-safety agency lead records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## US Law Enforcement, Corrections & Public Safety Leads Scraper

Build the **complete map of US public-safety agencies** — every **law enforcement agency** (local & municipal police, sheriff's offices, state police & highway patrol, federal, tribal and campus police), every **correctional facility** (prisons, jails & detention centers), plus optional **EMS / ambulance stations** and **911 / emergency-operations centers** — in one clean, structured dataset. Each record is a ready-to-use **B2B lead**: agency name, full address, phone, agency type, staffing & capacity, NAICS, website, geo coordinates and a **0-100 lead score**.

Data comes straight from **official US government open data (HIFLD — Homeland Infrastructure Foundation-Level Data)**. No login, no cookies, no browser, no API key — fast, reliable extraction of ~23,000 law enforcement agencies, ~6,500 correctional facilities, ~42,000 EMS stations and ~5,900 emergency-operations centers.

### Why this scraper?

Generic "verified-email" lead scrapers grab a handful of agencies off Google Maps and miss the data that actually matters for selling to government. This actor reads the authoritative national registry directly and ships the **richest public-safety dataset in the category** — agency type, sworn-officer counts, inmate capacity & security level, EMS personnel & fleet, NAICS and geo — merged across four agency types into one unified schema.

| Data | Generic crawlers | This actor |
|---|---|---|
| Agency name, full address | partial | ✅ ~100% |
| Phone number | partial | ✅ ~90%+ |
| Agency **type** (police / sheriff / state / federal / tribal / campus) | ❌ | ✅ normalized |
| **Sworn-officer staffing** (full/part-time, civilians) | ❌ | ✅ law enforcement |
| Correctional **capacity & security level** | ❌ | ✅ corrections |
| EMS **personnel & fleet** (ambulances, trucks) | ❌ | ✅ EMS |
| **NAICS, county FIPS, geo coordinates** | ❌ | ✅ |
| Website | partial | ✅ when published |
| Lead score + lead signals | ❌ | ✅ 0-100 |
| One unified dataset across 4 agency types | ❌ | ✅ |
| Only-new / changed monitoring | ❌ | ✅ monitor mode |

### Who buys this data?

Public-safety and govtech vendors sell into a **high-budget, hard-to-list market**. This is the prospecting list:

- **Govtech & public-safety software** — CAD / RMS / dispatch, records management, evidence, ALPR, body-worn cameras, drones, real-time crime centers.
- **Corrections vendors** — inmate communications, commissary, correctional healthcare, food service, JMS / offender-management software, tablets.
- **EMS & fleet** — ambulance manufacturers, EMS software / ePCR, medical supplies, vehicle upfitters, fuel & telematics.
- **Equipment & uniforms** — duty gear, firearms & less-lethal, fleet vehicles, radios & communications.
- **Training, consulting & staffing** — academies, policy/compliance (e.g. accreditation), recruiting, grant-writing.
- **Grants, GIS & analytics** — anyone targeting agencies by size, type, jurisdiction or geography.

### Use cases

- **Lead generation** — export every agency in a state or county with type, size and phone, then load your CRM or outreach sequence.
- **Territory & TAM planning** — size your market by agency type, sworn-officer count or inmate capacity.
- **Government RFP / bid targeting** — build account lists by jurisdiction and agency category.
- **Competitive & market research** — map the full universe of agencies in a region, not just the ones with a website.
- **Data enrichment** — append agency type, NAICS, county FIPS and geo to your existing account list.

### How to use

1. [Sign up for Apify](https://console.apify.com/sign-up) — the free plan is enough to try this actor.
2. Open the **US Law Enforcement, Corrections & Public Safety Leads Scraper**, pick your **categories** (Law enforcement + Corrections by default) and add a **state** (e.g. `TX`) to target a market.
3. Click **Start** and watch results stream into the dataset table.
4. **Export** as JSON, CSV, Excel, XML or RSS — or pull results programmatically via the [Apify API](https://docs.apify.com/api/v2).

### Input

```json
{
    "categories": ["lawEnforcement", "corrections"],
    "states": ["TX"],
    "agencyTypes": ["Sheriff", "Local"],
    "minSwornOfficers": 25,
    "hasPhone": true,
    "maxResults": 1000,
    "sortBy": "leadScore"
}
```

- **categories** *(default `lawEnforcement` + `corrections`)* — any of `lawEnforcement`, `corrections`, `ems`, `eoc`. EMS and 911/EOC are optional add-ons (fire departments are in our separate [US Fire Department Leads](https://apify.com/scrapesage/us-fire-department-leads-scraper) actor).
- **states / cities / counties / zipCodes** — location filters (USPS state codes, case-insensitive city/county contains, ZIP prefix). All optional, combine with AND.
- **nameQuery** — only agencies whose name contains this text.
- **agencyTypes** — keep only matching types (e.g. `Sheriff`, `State Police`, `Campus`, `Tribal`, `Federal`, `County Jail`, `State Prison`).
- **tribalOnly** — only tribal / Native American law enforcement.
- **minSwornOfficers / minInmateCapacity** — size thresholds to target larger, higher-budget agencies.
- **hasPhone / hasWebsite / hasEmail** — require a contact channel.
- **maxResults** *(default 1000)* — top-N by your sort order.
- **sortBy** *(default `leadScore`)* — `leadScore`, `agencySize`, `name`, `state`, or `source`.
- **monitorMode / monitorKey** — only return new / changed agencies across runs (see below).
- **proxyConfiguration** — optional; HIFLD needs no proxy (default off is fastest).

### Output

By default you get **one clean, dense table of agencies** — every column applies to every row. A law-enforcement record:

```json
{
    "category": "lawEnforcement",
    "categoryLabel": "Law enforcement agency",
    "name": "Travis County Sheriffs Office",
    "agencyType": "Sheriff",
    "rawAgencyType": "COUNTY SHERIFFS OFFICE",
    "address1": "5555 AIRPORT BLVD",
    "city": "Austin",
    "county": "Travis",
    "countyFips": "48453",
    "state": "TX",
    "zip": "78751",
    "fullAddress": "5555 AIRPORT BLVD, Austin, TX, 78751",
    "latitude": 30.31, "longitude": -97.71,
    "phone": "(512) 854-9770",
    "website": "http://www.tcsheriff.org",
    "naicsCode": "922120",
    "naicsDescription": "Police Protection",
    "isTribal": false,
    "totalSwornOfficers": 1480,
    "staffing": { "fullTimeSwornOfficers": 1450, "partTimeSwornOfficers": 30, "fullTimeCivilians": 620 },
    "bestPhone": "(512) 854-9770",
    "leadScore": 88,
    "leadSignals": ["Has phone number", "Has website", "Large agency (100+ sworn officers)", "Primary policing agency"],
    "mapUrl": "https://www.google.com/maps/search/?api=1&query=30.31,-97.71",
    "sourceDatasetUrl": "https://hifld-geoplatform.hub.arcgis.com/datasets/local-law-enforcement-locations",
    "scrapedAt": "2026-06-21T12:00:00.000Z",
    "sourceFields": { "...": "every original HIFLD attribute, untouched" }
}
```

Correctional facilities add `inmateCapacity`, `securityLevel` and `inmatePopulation`. EMS records add `personnel`, `fleet` (ambulances, trucks), `serviceLevel` and `owner`. 911/EOC records add `email`, `fax`, `dispatchPhone`, `governmentLevel`, `totalStaff` and `capacity`. Every record also carries a full `sourceFields` object with the **complete, untouched original attributes**, so nothing is ever lost.

#### What to expect (field coverage)

HIFLD is government-maintained, so a few fields are populated only when the source agency reported them. Typical coverage:

| Category | Always present | Usually present | Present when reported |
|---|---|---|---|
| **Law enforcement** | name, address, state, type | phone ~90%, county/FIPS, NAICS | sworn-officer counts, website |
| **Corrections** | name, address, state, type | phone, capacity | security level, website |
| **EMS** | name, address, state | phone, type | personnel, fleet, service level, owner |
| **911 / EOC** | name, address, state | phone | email, fax, staff, capacity, gov level |

A blank field means the source didn't publish it for that record — not that scraping failed. Nothing is dropped.

### Monitor mode — only new & changed agencies

Turn on **monitorMode** and the actor remembers every agency it has returned (in a per-key store). On later runs it emits only **new** or **changed** records, each tagged with a `monitorEvent` of `new` or `updated` — perfect for catching newly added agencies, facility openings, contact changes and capacity changes.

This **complements** Apify's built-in scheduler rather than conflicting with it: a [Schedule](https://docs.apify.com/platform/schedules) decides *when* the actor runs; monitor mode decides *what's new* each time. Use a distinct `monitorKey` per saved search (e.g. `tx-sheriffs`) so each market tracks independently.

### Automate & schedule

Run this actor on autopilot and pull results into your own stack:

- **[Apify API](https://docs.apify.com/api/v2)** — start runs, fetch datasets, manage schedules over REST.
- **[apify-client for JavaScript](https://docs.apify.com/api/client/js/)** and **[Python](https://docs.apify.com/api/client/python/)** — official SDKs.
- **[Schedules](https://docs.apify.com/platform/schedules)** — run it weekly/monthly with monitor mode to capture new agencies as the registry updates.
- **[Webhooks](https://docs.apify.com/platform/integrations/webhooks)** — trigger downstream actions (CRM import, Slack alert, email sequence) the moment a run finishes.

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

const client = new ApifyClient({ token: 'MY_APIFY_TOKEN' });

const run = await client.actor('scrapesage/us-law-enforcement-leads').call({
    categories: ['lawEnforcement', 'corrections'],
    states: ['TX'],
    minSwornOfficers: 25,
    maxResults: 1000,
});

const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(`Got ${items.length} agencies`);
```

### Integrate with any app

Connect the dataset to 5,000+ apps — no code required:

- **[Make](https://docs.apify.com/platform/integrations/make)** — multi-step automation scenarios.
- **[Zapier](https://docs.apify.com/platform/integrations/zapier)** — push new agency leads straight into your CRM.
- **[Slack](https://docs.apify.com/platform/integrations/slack)** — get notified when monitored markets add agencies.
- **[Google Drive / Sheets](https://docs.apify.com/platform/integrations/drive)** — auto-export every run to a spreadsheet.
- **[Airbyte](https://docs.apify.com/platform/integrations/airbyte)** — pipe results into your data warehouse.
- **[GitHub](https://docs.apify.com/platform/integrations/github)** — trigger runs from commits or releases.

### Use with AI assistants (MCP)

The output is clean, LLM-ready JSON. Call this actor from Claude, ChatGPT or any agent framework through the **[Apify MCP server](https://docs.apify.com/platform/integrations/mcp)** — ask your assistant to "list every sheriff's office in Texas with 25+ sworn officers and a phone number" and let it run the scraper for you.

### Agent-ready: autonomous payments (x402 & Skyfire)

This actor is **agent-ready** — AI agents can discover it, run it, and **pay for it autonomously**, with no Apify account and no human in the loop. It uses [pay-per-event](https://docs.apify.com/platform/actors/publishing/monetize/pay-per-event) pricing and [limited permissions](https://docs.apify.com/platform/actors/development/permissions), so it qualifies for Apify's agentic-payment standards:

- **[x402](https://docs.apify.com/platform/integrations/x402)** — an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp) — no account, no API key.
- **[Skyfire](https://docs.apify.com/platform/integrations/skyfire)** — agent-to-service payments for fully autonomous AI-agent workflows.

Building an AI agent, MCP tool, or autonomous data pipeline? This scraper is ready to plug in and pay as it goes.

### More US B2B lead scrapers from scrapesage

Build a complete **government, public-sector & B2B lead-gen stack** from official registries:

- **[US Fire Department Leads Scraper](https://apify.com/scrapesage/us-fire-department-leads-scraper)** — fire & rescue departments from the USFA registry (the public-safety sibling to this actor).
- **[US Healthcare Facility Leads Scraper](https://apify.com/scrapesage/us-healthcare-facility-leads-scraper)** — hospitals, ASCs, dialysis, SNFs, home health & hospice from CMS.
- **[US Schools Scraper](https://apify.com/scrapesage/us-schools-scraper)** — K-12 schools, districts & colleges from NCES + IPEDS.
- **[US Property Records Scraper](https://apify.com/scrapesage/us-property-records-scraper)** — parcels, owners & mailing addresses from county assessors.
- **[US Business Formation Scraper](https://apify.com/scrapesage/us-business-formation-scraper)** — newly registered LLCs & corporations from Secretary of State filings.
- **[FMCSA Trucking Scraper](https://apify.com/scrapesage/fmcsa-trucking-scraper)** — motor carriers, fleets & safety data.
- **[US Contractor License Scraper](https://apify.com/scrapesage/us-contractor-license-scraper)** — licensed contractors across states.
- **[NPI Registry Scraper](https://apify.com/scrapesage/npi-nppes-scraper)** — US healthcare provider NPI directory.
- **[SAM.gov Scraper](https://apify.com/scrapesage/sam-gov-scraper)** — federal contract opportunities.
- **[Website Contact Scraper](https://apify.com/scrapesage/website-contact-scraper)** — enrich any agency website with emails, phones & socials.

### Tips

- **Always set a `state`** (or city/county) — it filters server-side, so runs are faster and cheaper than scanning the whole country.
- **Target larger agencies** with `minSwornOfficers` (law enforcement) or `minInmateCapacity` (corrections) — bigger agencies mean bigger budgets.
- **Need emails?** Turn on the **911 / EOC** category — emergency-operations centers frequently publish an email and fax. Then run the [Website Contact Scraper](https://apify.com/scrapesage/website-contact-scraper) over the `website` field to enrich the rest.
- **Recurring monitoring**: combine [Schedules](https://docs.apify.com/platform/schedules) with `monitorMode` to track a state and only pull new or changed agencies.

### FAQ

**Where does the data come from?** Official US government **HIFLD (Homeland Infrastructure Foundation-Level Data)** open datasets, served as keyless ArcGIS feature services on the FEMA / HIFLD GeoPlatform. The underlying sources include the DOJ/BJS law-enforcement census and the HIFLD prison, EMS and EOC layers.

**Does it need an API key or login?** No. Everything is public, keyless and no-browser.

**Does it include emails?** Law-enforcement and corrections records are phone-and-website oriented (government agencies rarely publish a generic email in these registries). The **911 / EOC** category often does include email — and you can enrich any record's `website` with our [Website Contact Scraper](https://apify.com/scrapesage/website-contact-scraper).

**Are fire departments included?** Not in the default categories — fire & rescue departments have their own, richer source and live in our [US Fire Department Leads Scraper](https://apify.com/scrapesage/us-fire-department-leads-scraper). EMS stations (which overlap some fire-based EMS) are available here as an optional category.

**How fresh is it?** HIFLD layers update periodically (not daily). Agency names, addresses and phones are stable; use `monitorMode` on a schedule to capture changes as they land.

**Can I export to Google Sheets, CSV or Excel?** Yes — one click in the dataset view, or automatically on every run via the [Google Drive integration](https://docs.apify.com/platform/integrations/drive).

**A field is empty — why?** The source agency didn't report it. Fields are blank only when the data isn't published — never because the scraper skipped it; the full original record is always in `sourceFields`.

**Is this legal?** The actor collects publicly available government data only. You're responsible for using it in compliance with applicable laws and the source terms.

### Need help?

Open an issue on the actor's **Issues** tab, or visit the [Apify help center](https://help.apify.com/). Feature requests are welcome — this actor is actively maintained.

# Actor input Schema

## `categories` (type: `array`):

Which public-safety agency types to pull. <b>Law enforcement</b> (~23k local/county/state/federal/tribal/campus police agencies — with sworn-officer staffing) and <b>Corrections</b> (~6k prisons, jails & detention facilities — with capacity & security level) are the core. <b>EMS / ambulance</b> (~42k stations) and <b>911 / Emergency Operations Centers</b> (~6k, many with email) are optional add-ons. Note: fire departments are covered by our separate US Fire Department Leads actor.

## `states` (type: `array`):

Filter by state — two-letter USPS codes, e.g. <code>CA</code>, <code>TX</code>, <code>NY</code>, <code>FL</code>. Leave empty for all states & territories (slower; scans the whole country).

## `cities` (type: `array`):

Filter by city name (case-insensitive contains), e.g. <code>Houston</code>, <code>Phoenix</code>. Combine with a state for accuracy.

## `counties` (type: `array`):

Filter by county name (case-insensitive contains), e.g. <code>Harris</code>, <code>Maricopa</code>.

## `zipCodes` (type: `array`):

Filter by ZIP — full ZIP (<code>77002</code>) or a prefix (<code>770</code> matches all 770xx).

## `nameQuery` (type: `string`):

Only return agencies whose name contains this text (case-insensitive), e.g. <code>county</code>, <code>university</code>, or a specific agency name.

## `agencyTypes` (type: `array`):

Keep only agencies whose normalized or raw type contains one of these words (case-insensitive), e.g. <code>Sheriff</code>, <code>State Police</code>, <code>Campus</code>, <code>Tribal</code>, <code>Federal</code>, <code>County Jail</code>, <code>State Prison</code>. Leave empty for all.

## `tribalOnly` (type: `boolean`):

Only return tribal / Native American law enforcement agencies.

## `minSwornOfficers` (type: `integer`):

Only law-enforcement agencies with at least this many sworn officers (full-time + part-time). Great for targeting larger, higher-budget departments. E.g. <code>25</code>.

## `minInmateCapacity` (type: `integer`):

Only correctional facilities with at least this rated inmate capacity. E.g. <code>250</code>.

## `hasPhone` (type: `boolean`):

Only return agencies that include a phone number.

## `hasWebsite` (type: `boolean`):

Only return agencies that include a website.

## `hasEmail` (type: `boolean`):

Only return agencies that include an email address (primarily 911 / Emergency Operations Centers).

## `maxResults` (type: `integer`):

Maximum number of agency records to return. The actor ranks by your chosen sort order and returns the top N. Lower this for quick, cheap test runs.

## `sortBy` (type: `string`):

Ordering of the returned records.

## `deduplicateResults` (type: `boolean`):

Drop duplicate agencies (by category + agency ID) within a run.

## `monitorMode` (type: `boolean`):

Remember which agencies were already returned (in a per-key store) and, on later runs, emit only <b>new</b> or <b>changed</b> records — each tagged with <code>monitorEvent</code>. Combine with Apify Schedules to auto-detect new agencies, openings, contact changes and capacity changes. Does not conflict with scheduling — it simply de-duplicates across runs.

## `monitorKey` (type: `string`):

Names the memory used by monitor mode. Use a different key per saved search / market (e.g. <code>tx-sheriffs</code>) so they track independently.

## `proxyConfiguration` (type: `object`):

Proxy settings. HIFLD open data is served directly from US government ArcGIS endpoints and needs no proxy — the default (no proxy) is fastest. You may enable Apify Proxy if you prefer.

## Actor input object example

```json
{
  "categories": [
    "lawEnforcement",
    "corrections"
  ],
  "states": [
    "WY"
  ],
  "tribalOnly": false,
  "hasPhone": false,
  "hasWebsite": false,
  "hasEmail": false,
  "maxResults": 1000,
  "sortBy": "leadScore",
  "deduplicateResults": true,
  "monitorMode": false,
  "monitorKey": "default",
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

All scraped law-enforcement, corrections, EMS and EOC agency records in the default dataset, each with firmographics, contacts, agency type, size signals and a lead score.

# 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 = {
    "categories": [
        "lawEnforcement",
        "corrections"
    ],
    "states": [
        "WY"
    ],
    "maxResults": 1000
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapesage/us-law-enforcement-leads").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 = {
    "categories": [
        "lawEnforcement",
        "corrections",
    ],
    "states": ["WY"],
    "maxResults": 1000,
}

# Run the Actor and wait for it to finish
run = client.actor("scrapesage/us-law-enforcement-leads").call(run_input=run_input)

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

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

```

## CLI example

```bash
echo '{
  "categories": [
    "lawEnforcement",
    "corrections"
  ],
  "states": [
    "WY"
  ],
  "maxResults": 1000
}' |
apify call scrapesage/us-law-enforcement-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=scrapesage/us-law-enforcement-leads",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/zNW7Fl0l1GqkDKW2A/builds/7TBLAWIJHN7iuC5WH/openapi.json