# US Airport & Aviation Facility Leads Scraper (FAA) (`scrapesage/us-aviation-facility-leads`) Actor

Scrape every US airport, heliport & seaplane base from the official FAA NASR database: facility name, FAA/ICAO identifier, type, public/private use, owner & manager names with phone numbers, fuel, runways, FAR Part 139 status, services, GPS, lead score & monitoring. No browser, no API key.

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

## Pricing

from $3.00 / 1,000 aviation facility 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 Airport & Aviation Facility Leads Scraper (FAA)

Extract the **complete U.S. landing-facility universe** straight from the **official FAA NASR (National Airspace System Resources) database** — every **airport, heliport, seaplane base, gliderport, ultralight and balloonport** with its **facility name, FAA & ICAO identifier, type, public/private use, owner and manager names with phone numbers and addresses, fuel types, runways, FAR Part 139 certification, control tower, repair services, GPS coordinates and a lead score**. Group facilities into **owner / operator portfolios** to see who runs what, where.

No login, no cookies, no browser, no API key — fast, reliable extraction direct from the FAA's public 28-day NASR subscription files.

### Why this FAA airport scraper?

Other aviation tools on the market are aircraft-registry lookups, recall feeds, or thin map layers that **strip the owner and manager contacts**. This actor pulls **every U.S. landing facility nationwide** into **one clean, richest-in-category dataset** — and it keeps the **owner & manager phone numbers** (present on ~98% of facilities) that the public map services drop. It adds an **owner-portfolio grouping mode**, a **lead score**, and a **monitor mode** that surfaces only newly-activated and changed facilities.

| Data | Map layers / generic tools | This actor |
|---|---|---|
| Airports, heliports **and** seaplane bases in one run | partial | ✅ |
| Facility name, FAA + ICAO identifier, type | ✅ | ✅ |
| Public vs private use & ownership | partial | ✅ |
| **Owner name + address + phone** | ❌ (dropped) | ✅ ~96% |
| **Manager name + address + phone** | ❌ (dropped) | ✅ ~96% |
| Fuel types on field (FBO signal) | ❌ | ✅ |
| Runways (length, width, surface, lights) | partial | ✅ |
| FAR Part 139 certification (airline service) | ❌ | ✅ |
| Control tower, UNICOM/CTAF, repair services | ❌ | ✅ |
| GPS coordinates, elevation, sectional chart | ✅ | ✅ |
| **Owner-portfolio grouping** (facility count, types, states) | ❌ | ✅ |
| Lead score + lead signals | ❌ | ✅ |
| **Monitor mode** (only new/changed) | ❌ | ✅ |
| Nationwide (50 states + DC + territories, ~19,400) | ❌ | ✅ |

### Use cases

- **Aviation fuel & FBO services** — filter to facilities that sell fuel (~3,900) and target the owner/manager directly for Jet A, 100LL, contract fuel, line service, and ground-support equipment.
- **Aviation insurance & finance** — every public and **private** airfield owner and manager with a phone number: airport liability, hangar, and aircraft insurance prospecting.
- **Hangar, construction & engineering** — coordinates, runway length/surface, acreage, and ownership for site work, pavement, lighting, and hangar development bids.
- **Airport management software & GovTech** — target **public-use airports and FAR Part 139** airports plus the cities, counties and authorities that own them (owner-portfolio mode).
- **Aircraft sales, charter & flight training** — find airfields by runway length, fuel, and based-facility type to place aircraft, charter, and instruction.
- **Drone / UAS & survey services** — map heliports and airfields by location and ownership for operations planning and outreach.
- **Market & competitive research** — map facility counts, fuel availability and ownership by state, county and owner.

### 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 Airport & Aviation Facility Leads Scraper**, choose your **states** (leave empty for all of the U.S.) and **facility types**, and pick an **output mode** — `facilities` (one row per airport/heliport) or `owners` (grouped portfolios).
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
{
    "states": ["WY", "MT"],
    "facilityTypes": ["AIRPORT"],
    "hasFuelOnly": true,
    "sortBy": "leadScore",
    "maxResults": 1000,
    "monitorMode": false
}
```

- **outputMode** *(default `facilities`)* — `facilities` returns one record per airport/heliport/seaplane base; `owners` aggregates facilities by owner into operator/authority portfolios.
- **states** *(default all)* — two-letter state/territory codes; empty scans all 50 states + DC + territories (~19,400 facilities).
- **facilityTypes** *(default all)* — `AIRPORT`, `HELIPORT`, `SEAPLANE BASE`, `GLIDERPORT`, `ULTRALIGHT`, `BALLOONPORT`.
- **publicUseOnly** *(default false)* — only public-use facilities. Leave OFF to also capture the ~14,000 **private** airfields, heliports and strips (owners are individuals, farms and companies — great for aircraft, hangar and insurance leads).
- **activeOnly** *(default true)* — only operational facilities. Turn OFF to include closed facilities.
- **hasFuelOnly** — only facilities that sell fuel (the strongest on-field FBO signal).
- **far139Only** — only FAR Part 139 certificated airports (commercial / airline service, ~520).
- **hasPhoneOnly** — only facilities with an owner or manager phone on file.
- **minRunwayFt** — minimum longest-runway length (e.g. 5000 to target jet-capable airports).
- **cityQuery / nameQuery / ownerQuery** — substring search by city, keyword (name/city/owner/ID), or owner/manager name.
- **minLeadScore / sortBy / maxResults** — filter, order (`leadScore`, `runwayLength`, `newest`, `name`), and cap.
- **includeRemarks** *(default false)* — attach the FAA textual remarks (operational notes & cautions) per facility.
- **includeRawFields** *(default false)* — attach the complete raw fixed-width FAA record line so no source data is ever lost.
- **cycleDate** — optional; pin a specific FAA NASR 28-day cycle (e.g. `2026-06-11`). Empty = currently effective cycle.
- **monitorMode / monitorKey** — return only new/changed records across runs (see below).
- **proxyConfiguration** — optional; the FAA NFDC files download with no proxy.

### Output

By default you get **one clean table of aviation facilities** — every column applies to every row. Set `outputMode` to `owners` for grouped owner portfolios.

A facility record (`recordType: "aviationFacility"`):

```json
{
    "recordType": "aviationFacility",
    "siteNumber": "27754.*A",
    "faaIdentifier": "CPR",
    "icaoIdentifier": "KCPR",
    "facilityName": "Casper/Natrona County Intl",
    "facilityType": "AIRPORT",
    "city": "Casper",
    "state": "WY",
    "county": "Natrona",
    "latitude": 42.905875,
    "longitude": -106.463649,
    "elevationFt": 5344,
    "ownershipType": "Publicly owned",
    "facilityUse": "Public",
    "isPublicUse": true,
    "ownerName": "County Board Of Commissioners",
    "ownerAddress": "8500 Airport Parkway, Suite 208",
    "ownerCity": "Casper",
    "ownerStateCode": "WY",
    "ownerZip": "82604",
    "ownerPhone": "307-472-6688",
    "managerName": "Glenn Januska",
    "managerPhone": "307-472-6688",
    "phone": "307-472-6688",
    "hasPhone": true,
    "status": "Operational",
    "activationDate": "1943-11",
    "far139Certified": true,
    "fuelTypes": ["100LL", "A"],
    "hasFuel": true,
    "airframeRepair": "Major",
    "powerplantRepair": "Major",
    "hasControlTower": true,
    "unicomFreq": "122.950",
    "ctafFreq": "118.300",
    "runways": [
        { "id": "03/21", "lengthFt": 10165, "widthFt": 150, "surface": "ASPH-G", "surfaceType": "Asphalt", "edgeLights": "HIGH" }
    ],
    "runwayCount": 2,
    "longestRunwayFt": 10165,
    "nasrCycle": "2026-06-11",
    "detailUrl": "https://www.airnav.com/airport/CPR",
    "leadScore": 100,
    "leadSignals": ["Public-use facility", "Fuel on field (100LL, A)", "FAR Part 139 certified (commercial service)", "Control tower on field", "Jet-capable runway (10165 ft)", "Manager phone on file"]
}
```

An owner record (`recordType: "facilityOwnerProfile"`) carries `ownerName`, `ownerPhone`, `facilityCount`, `airports` / `heliports` / `seaplaneBases`, `publicUseFacilities`, `fueledFacilities`, `far139Facilities`, `stateCount`, `states`, `faaIdentifiers`, `maxRunwayFt`, and a `leadScore`.

#### What to expect (field coverage)

This is the official FAA NASR landing-facility database — the same public records the FAA publishes every 28 days.

| Field | Coverage |
|---|---|
| Facility name, FAA ID, type, city, state, status, GPS | ~100% |
| **Owner name & phone** | ~96% |
| **Manager name & phone** | ~96% (≥98% of facilities have at least one phone) |
| Fuel types on field | ~20% (every fueled facility — the FBO targets) |
| Runways (length, width, surface) | ~100% of airports |
| FAR Part 139 certification | ~520 commercial-service airports |
| ICAO identifier | airports with international service |

A blank field means the FAA didn't publish it for that facility — nothing is dropped, so you always get the richest dataset available. Turn on `includeRawFields` to keep every raw source value.

### 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, and manage schedules over REST.
- **[apify-client for JavaScript](https://docs.apify.com/api/client/js/)** and **[apify-client for Python](https://docs.apify.com/api/client/python/)** — official SDKs.
- **[Schedules](https://docs.apify.com/platform/schedules)** — run it on each new 28-day NASR cycle with **monitor mode on** to capture newly-activated and changed facilities automatically.
- **[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-aviation-facility-leads').call({
    states: ['CA'],
    hasFuelOnly: true,
    monitorMode: true,
});

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

**Monitor mode vs. Apify Schedules** — they are independent and work together. *Monitor mode* remembers what previous runs returned (per `monitorKey`) and emits only new/changed records; *Schedules* decide when the actor runs. Combine them for a hands-off feed of new and changed airports.

### 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 facility / owner leads straight into your CRM.
- **[Slack](https://docs.apify.com/platform/integrations/slack)** — get notified when a monitored state adds a facility.
- **[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 public airport in Texas that sells fuel, with its manager's 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 scrapers from scrapesage

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

- **[FAA Aircraft Registry Scraper](https://apify.com/scrapesage/faa-aircraft-registry-scraper)** — registered aircraft and their owners by N-number.
- **[FAA Airmen Certification Scraper](https://apify.com/scrapesage/faa-airmen-certification-scraper)** — certificated pilots and mechanics.
- **[FCC Broadcast Station & Owner Leads Scraper](https://apify.com/scrapesage/fcc-broadcast-scraper)** — AM/FM/TV stations and the companies that own them.
- **[FMCSA Trucking Scraper](https://apify.com/scrapesage/fmcsa-trucking-scraper)** — motor carriers and freight brokers with contact and safety data.
- **[US Business Formation Scraper](https://apify.com/scrapesage/us-business-formation-scraper)** — newly registered companies as fresh-business intent.
- **[GSA eLibrary Scraper](https://apify.com/scrapesage/gsa-elibrary-scraper)** — GSA Schedule contractors and their contacts.
- **[USASpending Scraper](https://apify.com/scrapesage/usaspending-scraper)** — federal contract and grant recipients.
- **[SBA Loan Leads Scraper](https://apify.com/scrapesage/sba-loan-leads-scraper)** — financed small businesses (7(a) & 504).

### Tips

- **Pick a single output mode** (`facilities` or `owners`) for a clean, fully-populated table that's perfect for direct export. Use the **Facilities**, **Contacts**, and **Facility owners** dataset views to switch focus.
- **Find FBOs**: set `hasFuelOnly: true` and `sortBy: "leadScore"` to surface fueled, public-use airports — the best targets for fuel, line service, and ground-support vendors.
- **Target jet airports**: set `minRunwayFt: 5000` (or `far139Only: true`) for the largest, highest-budget airports and authorities.
- **Mine private airfields**: leave `publicUseOnly` off to reach the ~14,000 privately-owned strips and heliports — owners are individuals, ranches, hospitals and companies.
- **Find an authority's footprint**: use `outputMode: "owners"` with an `ownerQuery` (e.g. "County" or "City of") to see every facility a government owns.
- **Recurring monitoring**: pair `monitorMode` with a [Schedule](https://docs.apify.com/platform/schedules) tied to the 28-day NASR cycle for an always-fresh feed of new and changed facilities.

### FAQ

**Where does the data come from?** The official FAA NASR (National Airspace System Resources) 28-day subscription — the public APT (landing facility) file the FAA publishes — normalized into one schema and enriched with a lead score and owner grouping.

**Does it need an FAA API or a key?** No. There's no login, key, or browser — the actor downloads the FAA's public NASR file directly and always resolves the currently effective 28-day cycle.

**Does every facility include a phone number?** About 98% do — the FAA publishes an owner and/or manager phone for nearly every facility. Public mapping layers strip these contacts; this actor keeps them.

**What's the difference vs. an aircraft registry scraper?** This actor covers the **physical airports, heliports and seaplane bases** (and the people who own and manage them). For registered **aircraft** and their owners, use our FAA Aircraft Registry Scraper; for **pilots and mechanics**, the FAA Airmen Certification Scraper.

**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).

**How do I monitor for new airports?** Turn on `monitorMode`, set a `monitorKey`, and create a [Schedule](https://docs.apify.com/platform/schedules); optionally add a [webhook](https://docs.apify.com/platform/integrations/webhooks) or [Zapier zap](https://docs.apify.com/platform/integrations/zapier) to push new records into your CRM.

**Is scraping this data legal?** This actor collects publicly available U.S. government data only. You're responsible for using it in compliance with applicable laws and the FAA's 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

## `outputMode` (type: `string`):

‘Aviation facilities’ returns one record per airport/heliport/seaplane base (with owner & manager contacts). ‘Facility owners (grouped)’ aggregates facilities by owner into portfolios (facility count, types, states) — ideal for airport authorities, government & M\&A targeting.

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

Two-letter state/territory codes (e.g. CA, TX, NY, AK, PR). Leave empty to scan all 50 states + DC + territories (~19,400 facilities).

## `facilityTypes` (type: `array`):

Limit to specific landing-facility types. Empty = all types.

## `publicUseOnly` (type: `boolean`):

Only return facilities open to the public (facility use = Public). Leave OFF to also include the ~14,000 private airfields, heliports & strips (owners are individuals, farms & companies — great for aircraft, hangar & insurance leads).

## `activeOnly` (type: `boolean`):

Only return facilities with an Operational status. Turn OFF to also include closed facilities.

## `hasFuelOnly` (type: `boolean`):

Only return facilities that sell fuel — the strongest signal of an on-field FBO / fuel operation (~3,900 facilities). Ideal for aviation-fuel, FBO and ground-service vendors.

## `far139Only` (type: `boolean`):

Only return airports certificated under FAR Part 139 (commercial passenger / airline service — ~520 airports). Highest-budget airport authorities.

## `hasPhoneOnly` (type: `boolean`):

Only return facilities that have an owner or manager phone number on file (~98% of facilities do).

## `minRunwayFt` (type: `integer`):

Only return facilities whose longest runway is at least this many feet (e.g. 5000 to target jet-capable airports).

## `cityQuery` (type: `string`):

Keep only facilities whose city contains this term (substring match).

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

Free-text keyword matched across facility name, city, owner name and FAA/ICAO identifier.

## `ownerQuery` (type: `string`):

Filter by owner or manager name — e.g. ‘County’, ‘City of’, ‘Aviation’, ‘University’. Substring match.

## `minLeadScore` (type: `integer`):

Only return records with a lead score (0–100) at or above this value.

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

Order of results before the max-results cap is applied.

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

Maximum number of records to return (facilities or owner profiles depending on output mode).

## `includeRemarks` (type: `boolean`):

Attach the FAA textual remarks (operational notes & cautions) for each facility as a remarks\[] array. Off by default to keep records lean.

## `includeRawFields` (type: `boolean`):

Attach the complete raw fixed-width FAA APT record line to every facility, so no source data is ever lost.

## `cycleDate` (type: `string`):

Optional. Pin a specific FAA NASR 28-day subscription cycle (e.g. 2026-06-11). Leave empty to auto-use the currently effective cycle.

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

Remember what was returned on previous runs (per monitor key) and emit only NEW facilities (or owners whose facility count changed). Perfect for a recurring Apify Schedule that feeds newly-activated airports & status changes into your CRM. Works alongside Apify scheduling — they are independent.

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

Names the saved monitor state, so different filter setups track new records independently. Use a distinct key per saved configuration.

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

Optional. The FAA NFDC open-data files download directly from Apify with no proxy; you can enable one if you prefer.

## Actor input object example

```json
{
  "outputMode": "facilities",
  "states": [
    "WY"
  ],
  "facilityTypes": [],
  "publicUseOnly": false,
  "activeOnly": true,
  "hasFuelOnly": false,
  "far139Only": false,
  "hasPhoneOnly": false,
  "sortBy": "leadScore",
  "maxResults": 1000,
  "includeRemarks": false,
  "includeRawFields": false,
  "monitorMode": false,
  "monitorKey": "default",
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

All scraped FAA aviation-facility or owner-profile records in the default dataset.

# 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 = {
    "states": [
        "WY"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapesage/us-aviation-facility-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 = { "states": ["WY"] }

# Run the Actor and wait for it to finish
run = client.actor("scrapesage/us-aviation-facility-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 '{
  "states": [
    "WY"
  ]
}' |
apify call scrapesage/us-aviation-facility-leads --silent --output-dataset

```

## MCP server setup

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

```

## OpenAPI specification

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