FTC Enforcement Actions Scraper

Scrape FTC enforcement actions, cases, proceedings, matter numbers, statuses, summaries, updates, and detail links from the FTC Legal Library.

What does FTC Enforcement Actions Scraper do?

FTC Enforcement Actions Scraper turns the public FTC cases and proceedings listing into structured data.

It extracts case titles, source URLs, record types, summaries, action types, last updated dates, matter/file numbers, case statuses, and optional detail-page links.

Use it when you need repeatable monitoring of FTC enforcement activity without manually opening the FTC website.

Who is it for?

• ⚖️ Law firms tracking FTC litigation and administrative proceedings.
• 🛡️ Compliance teams monitoring regulatory risk by company, topic, or status.
• 📰 Journalists following new FTC enforcement developments.
• 📊 Risk intelligence teams building alerts and dashboards.
• 🏛️ Policy researchers studying competition and consumer protection enforcement.

Why use this actor?

The FTC site is public, but the data is spread across paginated HTML pages and case detail pages.

This actor gives you a clean dataset that can be exported to JSON, CSV, Excel, or connected to downstream workflows.

You can run it on a schedule to monitor new cases and filter by keyword, action type, status, matter number, or date range.

Data you can extract

Field	Description
title	FTC case or proceeding title
detailUrl	Canonical FTC detail page URL
recordTypes	FTC record type labels
summary	Listing or detail summary
actionType	Federal, Administrative, or Process Enforcement when available
lastUpdated	Human-readable FTC last updated date
lastUpdatedIso	ISO timestamp from FTC markup when available
matterNumber	FTC Matter/File Number
caseStatus	Pending, closed, under order, or other FTC status
topics	Topic labels found on detail pages
documents	Related FTC document links when detail fetching is enabled
pressReleases	Related FTC press release links when detail fetching is enabled
sourceUrl	Listing URL that produced the record
scrapedAt	Scrape timestamp

How much does it cost to scrape FTC enforcement actions?

This actor uses pay-per-event pricing.

You pay a small start fee per run and a per-record charge for each FTC case or proceeding saved.

The default input is intentionally small so your first run is inexpensive.

For large monitoring jobs, set maxItems to the number of records you actually need.

How to scrape FTC enforcement actions

1. Open the actor on Apify.
2. Keep the prefilled FTC cases/proceedings start URL.
3. Enter a keyword such as a company name, product category, or matter number.
4. Optionally select action types or case status.
5. Set maxItems.
6. Turn on includeDetails if you need documents and press releases.
7. Run the actor.
8. Download the dataset or connect it to your workflow.

Input options

Start URLs

Use startUrls to provide FTC cases/proceedings listing URLs.

The default URL is:

https://www.ftc.gov/legal-library/browse/cases-proceedings

Keyword search

Use search to search by company name, individual name, keyword, or case number.

Examples:

• Amazon
• Kochava
• data security
• merger

Action type filters

Use actionTypes to filter by FTC action type.

Supported values:

• Federal
• Administrative
• ProcessEnforcement

Case status filter

Use caseStatus to narrow the results.

Supported values include:

• pending
• closed
• under_order
• on_appeal

Matter number search

Use matterNumber when you already know the FTC Matter/File Number.

Date range

Use startDate and endDate in MM/DD/YYYY format.

Detail enrichment

Set includeDetails to true to fetch each case detail page.

This can add topics, documents, and press release links.

It is slower than listing-only mode because it performs one extra request per case.

Example input

{
  "startUrls": [
    { "url": "https://www.ftc.gov/legal-library/browse/cases-proceedings" }
  ],
  "search": "Amazon",
  "maxItems": 25,
  "includeDetails": false
}

Example output

{
  "title": "Amazon.com, Inc., U.S. v.",
  "detailUrl": "https://www.ftc.gov/legal-library/browse/cases-proceedings/252-3024-amazoncom-inc-us-v",
  "recordTypes": ["Cases and Proceedings"],
  "summary": "Amazon will pay $2.25 million in civil penalties...",
  "actionType": "Federal",
  "lastUpdated": "June 30, 2026",
  "lastUpdatedIso": "2026-06-30T12:00:00Z",
  "matterNumber": "252 3024",
  "caseStatus": "Pending",
  "topics": [],
  "documents": [],
  "pressReleases": [],
  "sourceUrl": "https://www.ftc.gov/legal-library/browse/cases-proceedings?...",
  "scrapedAt": "2026-07-01T00:00:00.000Z"
}

Tips for better results

• Use a company name for focused monitoring.
• Use caseStatus for workflows that only care about pending or active matters.
• Keep includeDetails off for fast broad scans.
• Turn includeDetails on for research packs, legal memos, or document collection.
• Use maxItems to control cost and runtime.

Common workflows

FTC company monitor

Schedule a daily run with a company name in search.

Export the dataset to your alerting or BI tool.

Pending cases dashboard

Run with caseStatus set to pending and sortBy set to newest.

Use the dataset to power a dashboard of current enforcement activity.

Matter-number lookup

Use matterNumber when a filing, press release, or client alert references a specific FTC number.

Document collection

Enable includeDetails for a narrow search to collect related FTC document links.

Integrations

You can connect this actor to:

• Google Sheets for regulatory trackers.
• Slack alerts through Apify integrations.
• Zapier or Make for compliance workflows.
• BI dashboards using the dataset API.
• Internal legal data lakes using Apify API clients.

API usage

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('automation-lab/ftc-enforcement-actions-scraper').call({
  search: 'Amazon',
  maxItems: 25,
});
console.log(run.defaultDatasetId);

Python

from apify_client import ApifyClient
import os

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('automation-lab/ftc-enforcement-actions-scraper').call({
    'search': 'Amazon',
    'maxItems': 25,
})
print(run['defaultDatasetId'])

cURL

curl -X POST "https://api.apify.com/v2/acts/automation-lab~ftc-enforcement-actions-scraper/runs?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"search":"Amazon","maxItems":25}'

Use with MCP

You can use this actor from Claude Desktop, Claude Code, or any MCP client through Apify MCP.

MCP server URL:

https://mcp.apify.com/?tools=automation-lab/ftc-enforcement-actions-scraper

Example prompts:

• "Run the FTC Enforcement Actions Scraper for Amazon and summarize pending matters."
• "Find FTC cases updated this month and export the dataset."
• "Collect detail links for FTC Kochava proceedings."

Data freshness

The actor reads the live FTC public website at run time.

If the FTC updates a case page, a new actor run can capture the changed listing metadata.

Reliability notes

The FTC listing is server-rendered HTML and does not require a browser for the core workflow.

The actor uses conservative HTTP requests and avoids unnecessary browser automation.

Legality and responsible use

This actor extracts public information from FTC.gov.

You should use the data responsibly, respect Apify and FTC website terms, and avoid excessive run frequency.

The actor does not bypass authentication, paywalls, or private systems.

FAQ and troubleshooting

Why did I get fewer records than maxItems?

Your filters may match fewer FTC records than the requested limit.

Try removing a filter or using a broader keyword.

Why are documents empty?

Documents are only collected when includeDetails is enabled and the FTC detail page exposes relevant links.

Why is the run slower with details enabled?

Detail mode opens every individual FTC case page, which adds one HTTP request per record.

Related scrapers

Explore other Automation Lab actors for regulatory, legal, and public-record monitoring:

• https://apify.com/automation-lab/sec-litigation-releases-scraper
• https://apify.com/automation-lab/fda-warning-letters-scraper
• https://apify.com/automation-lab/courtlistener-federal-docket-scraper

Changelog

0.1

Initial version with FTC listing scraping, filters, pagination, optional detail enrichment, and pay-per-event output.

Support

If you need a field from FTC detail pages that is not currently included, open an Apify issue with an example FTC URL and the expected field.

Maintained source

This actor targets the official FTC Legal Library cases/proceedings pages.

Output guarantees

Each record includes title, detailUrl, sourceUrl, and scrapedAt when the FTC listing card contains a valid case link.

Optional fields may be null or empty arrays when the FTC page does not expose that information.

Performance guidance

Listing-only mode is best for broad scans.

Detail mode is best for smaller, high-value legal research jobs.

Scheduling guidance

For monitoring workflows, schedule a daily run with a targeted keyword and moderate maxItems.

For quarterly research exports, run a broader query with a higher maxItems value.