SEC Litigation Releases Scraper

Track SEC litigation releases from the official U.S. Securities and Exchange Commission website. The actor extracts release numbers, dates, respondents, case references, summaries, detail-page body text, and related SEC complaint/order PDF links.

Use it as a repeatable SEC enforcement monitoring feed for legal research, compliance alerts, securities-litigation analysis, market-risk workflows, and financial-data enrichment.

What does SEC Litigation Releases Scraper do?

SEC Litigation Releases Scraper reads the public SEC Litigation Releases listing and follows each release detail page.

It saves one dataset item per litigation release.

Each item can include the official release number, release date, respondent or entity name, SEC detail URL, summary paragraph, full body text, docket candidates, case caption references, related document links, and PDF URLs.

The actor is HTTP-first and uses polite request delays by default.

Who is it for?

SEC Litigation Releases Scraper is for legal, compliance, and financial-risk teams that need structured SEC enforcement/litigation monitoring without manually checking the SEC website.

Who is SEC Litigation Releases Scraper for?

• ⚖️ Securities litigators tracking new SEC enforcement cases.
• 🧾 Compliance teams monitoring newly filed SEC civil actions.
• 📈 Investor-risk teams watching respondents, issuers, executives, and market-manipulation allegations.
• 🗃️ Financial-data vendors building structured enforcement datasets.
• 🔔 Monitoring teams that need scheduled alerts for newly published SEC releases.
• 🧑‍💼 Investigators who need complaint and judgment PDF links next to each release.

Why use this SEC litigation releases extractor?

The SEC page is public, but manual monitoring is repetitive.

This actor turns the listing and detail pages into structured JSON, CSV, Excel, or API-ready records.

You can schedule it daily, filter by date/year/month, and integrate the output into alerts, databases, dashboards, or legal review queues.

Data extracted

Field	Description
releaseNumber	Official SEC litigation release number such as LR-26574.
releaseDate	Release date in ISO format when available.
releaseTitle	SEC release title or respondent name.
respondents	Respondent/entity names extracted from listing/detail titles.
detailUrl	Canonical SEC release detail URL.
summary	First substantive detail-page paragraph.
bodyText	Full release text when enabled.
docketNumbers	Court docket/case number candidates.
caseReferences	Case caption references such as SEC v. ....
documentLinks	Related complaint, judgment, order, and PDF links.
pdfUrls	Convenience array of SEC PDF URLs.
sourceListingUrl	Listing page where the release was discovered.
scrapedAt	Timestamp of extraction.

How much does it cost to scrape SEC litigation releases?

This actor uses pay-per-event pricing.

There is a small start fee per run and a per-release fee for each dataset item saved.

Charge event	FREE	BRONZE	SILVER	GOLD	PLATINUM	DIAMOND
Run start	$0.005	$0.005	$0.005	$0.005	$0.005	$0.005
SEC litigation release saved	$0.000065449	$0.000056912	$0.000044392	$0.000034147	$0.000022765	$0.000015935

Example cost estimates before Apify platform free credits or plan discounts:

Run size	FREE estimate	BRONZE estimate	Notes
25 releases	about $0.0066	about $0.0064	Good for a quick smoke test.
100 releases	about $0.0115	about $0.0107	Typical scheduled monitoring run.
1,000 releases	about $0.0704	about $0.0619	Historical backfill or larger compliance export.

Apify free-plan users can run small tests cheaply: a 100-release monitoring run is roughly one cent in actor event charges, plus any normal Apify platform resource usage shown on your run page.

The default input is intentionally modest so first runs stay inexpensive.

For large historical backfills, increase maxItems and use year/month filters to control scope.

How to scrape SEC litigation releases

1. Open the actor on Apify.
2. Keep maxItems at 100 for a realistic monitoring run, or lower it for a quick test.
3. Optionally set year, month, dateFrom, or dateTo.
4. Leave startUrls empty to use the latest official SEC listing.
5. Keep includeBodyText enabled if you want legal text for downstream analysis.
6. Run the actor.
7. Export results as JSON, CSV, Excel, XML, RSS, or via the Apify API.

Input options

maxItems

Maximum number of SEC litigation releases to save.

Use 25 for a smoke test, 100 for scheduled monitoring, or higher for backfills.

year and month

Optional SEC listing filters.

Use All for current monitoring across the default listing.

dateFrom and dateTo

Optional inclusive ISO date filters.

These are useful when your schedule overlaps and you only want a specific monitoring window.

startUrls

Optional advanced source control.

You can provide an SEC litigation listing URL or a specific SEC litigation release URL.

includeBodyText

When enabled, the actor stores full detail-page body text.

Disable it for smaller exports when you only need metadata and document URLs.

includePdfText

This version collects SEC PDF links.

Full PDF text extraction is not enabled by default because legal PDFs vary and can increase compute cost.

requestDelayMs

Adds a polite delay between SEC detail requests.

The default is 250 ms.

proxyConfiguration

SEC is normally reachable without proxies.

Enable Apify Proxy only if your network environment is blocked.

Example input

{
  "maxItems": 100,
  "year": "All",
  "month": "All",
  "dateFrom": "2026-01-01",
  "includeBodyText": true,
  "includePdfText": false,
  "requestDelayMs": 250
}

Example output

{
  "releaseNumber": "LR-26574",
  "releaseDate": "2026-06-25",
  "releaseTitle": "Mingran Wang",
  "respondents": ["Mingran Wang"],
  "detailUrl": "https://www.sec.gov/enforcement-litigation/litigation-releases/lr-26574",
  "summary": "On June 24, 2026, the Securities and Exchange Commission filed settled charges...",
  "docketNumbers": ["No. 4:26-cv-06291 (N.D. Cal. filed June 24, 2026)"],
  "caseReferences": ["Securities and Exchange Commission v. Mingran Wang"],
  "pdfUrls": ["https://www.sec.gov/files/litigation/complaints/2026/comp26574.pdf"],
  "scrapedAt": "2026-06-29T00:00:00.000Z"
}

Tips for monitoring workflows

• Schedule a daily run with maxItems around 100.
• Use dateFrom to limit exports to your review period.
• Deduplicate downstream by releaseNumber or detailUrl.
• Keep includeBodyText enabled for NLP, summarization, and entity matching.
• Use pdfUrls to fetch complaints and judgments in a separate document-processing pipeline.

Integrations

You can connect the dataset to:

• Google Sheets for compliance review queues.
• Slack alerts through Apify webhooks.
• Airtable or Notion databases for manual triage.
• BigQuery, Snowflake, or Postgres for legal analytics.
• Vector databases for semantic search over SEC enforcement text.
• Internal watchlists matching respondent names and docket references.

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/sec-litigation-releases-scraper').call({
  maxItems: 100,
  includeBodyText: true
});
console.log(run.defaultDatasetId);

Python

from apify_client import ApifyClient

client = ApifyClient('YOUR_APIFY_TOKEN')
run = client.actor('automation-lab/sec-litigation-releases-scraper').call(run_input={
    'maxItems': 100,
    'includeBodyText': True,
})
print(run['defaultDatasetId'])

cURL

curl -X POST 'https://api.apify.com/v2/acts/automation-lab~sec-litigation-releases-scraper/runs?token=YOUR_APIFY_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{"maxItems":100,"includeBodyText":true}'

MCP integration

Use the Apify MCP server with Claude Code, Claude Desktop, Cursor, or VS Code-compatible MCP clients:

$https://mcp.apify.com/?tools=automation-lab/sec-litigation-releases-scraper

Claude Code CLI setup:

$claude mcp add apify-sec-litigation --transport http "https://mcp.apify.com/?tools=automation-lab/sec-litigation-releases-scraper"

Claude Desktop JSON config:

{
  "mcpServers": {
    "apify-sec-litigation": {
      "transport": "http",
      "url": "https://mcp.apify.com/?tools=automation-lab/sec-litigation-releases-scraper"
    }
  }
}

Cursor and VS Code use the same MCP server URL and HTTP transport. Add a server named apify-sec-litigation, set the transport to http, and use the URL above. If your client asks for JSON, use the Claude Desktop shape and paste it into the client's MCP configuration file.

Example prompts:

• "Run the SEC litigation releases scraper for the latest 100 releases and summarize new market-manipulation cases."
• "Find releases mentioning a specific respondent name in the dataset."
• "Export complaint PDF links from recent SEC litigation releases."

Related scrapers

Related Automation Lab actors may help with adjacent compliance workflows:

• https://apify.com/automation-lab/sec-13f-manager-quarterly-report-scraper
• https://apify.com/automation-lab/sec-investment-adviser-public-disclosure-scraper
• https://apify.com/automation-lab/fcc-ecfs-filings-scraper
• https://apify.com/automation-lab/fda-food-recalls-scraper

Legality and responsible use

The actor extracts public SEC web pages.

You are responsible for how you use the output.

Respect Apify terms, SEC website policies, and applicable laws.

Do not use scraped data to make legal, investment, or compliance decisions without appropriate professional review.

FAQ

Can I schedule this SEC litigation releases scraper?

Yes. Use an Apify schedule and deduplicate downstream by releaseNumber or detailUrl.

Does it download PDFs?

The actor collects official SEC PDF URLs. Download and PDF text extraction can be handled in a downstream document workflow.

Troubleshooting

Why did I get fewer releases than maxItems?

Your date/year/month filters may be too narrow, or the listing may not contain enough matching releases.

Broaden the filters or remove dateFrom/dateTo.

Why is bodyText empty?

Make sure includeBodyText is enabled.

If a SEC page changes structure, the actor will still save metadata and document links when available.

Do I need proxies?

Usually no.

The SEC listing is public and this actor uses a descriptive user agent and polite delay.

Changelog

0.1

Initial release with listing crawling, detail-page enrichment, summaries, body text, docket/case extraction, and related SEC document/PDF links.