# SEC Enforcement Tracker — Litigation, Proceedings & AAER (`foxlabs/sec-enforcement-actions`) Actor
Official SEC.gov enforcement feed: litigation releases, administrative proceedings and accounting & auditing enforcement (AAER). Filter by type, keyword, date. Defendants, release/file numbers, complaint links. Regulatory intel for compliance, securities lawyers, journalists.
- **URL**: https://apify.com/foxlabs/sec-enforcement-actions.md
- **Developed by:** [Berkan Kaplan](https://apify.com/foxlabs) (community)
- **Categories:** Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet
## Pricing
from $4.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.
Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event
## What's an Apify Actor?
Actors are a software tools running on the Apify platform, for all kinds of web data extraction and automation use cases.
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.
In JavaScript/TypeScript projects, use official [JavaScript/TypeScript client](https://docs.apify.com/api/client/js.md):
```bash
npm install apify-client
```
In Python projects, use official [Python client library](https://docs.apify.com/api/client/python.md):
```bash
pip install apify-client
```
In shell scripts, use [Apify CLI](https://docs.apify.com/cli/docs.md):
````bash
# MacOS / Linux
curl -fsSL https://apify.com/install-cli.sh | bash
# Windows
irm https://apify.com/install-cli.ps1 | iex
```bash
In AI frameworks, you might use the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp.md).
If your project is in a different language, use 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
SEC Enforcement Tracker pulls **enforcement actions straight from the official [U.S. Securities and Exchange Commission](https://www.sec.gov/enforcement-litigation) website** — **Litigation Releases** (civil court actions), **Administrative Proceedings** (in-house orders), and **Accounting & Auditing Enforcement Releases (AAER)** — as clean, structured JSON. One feed for **regulatory intelligence, compliance monitoring, securities-law research, and financial journalism**.
Because it runs on the Apify platform you get scheduling (daily enforcement alerts), API access, webhooks, and one-click export to JSON, CSV, or Excel — **no API key, no login, no proxies needed**.
### What does SEC Enforcement Tracker do?
It reads the SEC's official enforcement listings and returns each release as a flat JSON row: release type, release number, date, the **defendants/respondents named**, file number, comment deadlines, and links to the underlying complaint, order, or judgment documents. You can filter by **release type, defendant/respondent name, and date range**, optionally pull the **full release text**, and cap results to control cost.
The three feeds it covers:
- **Litigation Releases** — the SEC's civil actions filed in federal court (fraud, insider trading, Ponzi schemes, FCPA, crypto, etc.), with links to the filed complaint and final judgments.
- **Administrative Proceedings** — orders issued through the SEC's own administrative process, with file numbers, comment deadlines and distribution plans.
- **Accounting & Auditing Enforcement Releases (AAER)** — the subset of actions involving financial reporting, auditing and accountant/auditor misconduct.
### Why use SEC Enforcement Tracker?
- **Regulatory & compliance monitoring** — track every new enforcement action against companies, executives, advisers, auditors or funds in your coverage universe.
- **Securities-litigation intelligence** — surface defendants, case captions and complaint documents the moment a release is published; feed your case database or litigation-funding pipeline.
- **Due diligence & KYC** — screen a company or individual against the SEC's enforcement history by name.
- **Journalism & research** — build datasets of SEC enforcement activity over time, by type, defendant or topic.
- **Enforcement alerts on autopilot** — schedule a daily run filtered to your keywords and pipe results to Slack, email, a CRM, or an LLM via Make / Zapier / n8n.
### How to use SEC Enforcement Tracker
1. Click **Try for free**.
2. Pick **Release types** — leave empty for all three, or choose Litigation Releases / Administrative Proceedings / AAER.
3. Optionally add a **Keyword** (a defendant or company name), and a **Date range**.
4. Turn on **Include full release text** if you need the full body and document links.
5. Set **Max results** to control cost, click **Start**, then download the dataset or wire it into your pipeline.
### Input
| Field | Description |
|---|---|
| Release types | Litigation Releases, Administrative Proceedings, AAER — empty = all three |
| Keyword | Case-insensitive match on defendant/respondent names + release/file numbers |
| Date range | Last 24h / 7d / 30d / 90d / 365d / YTD / All time / Custom |
| Max results | Hard cap on rows across all types (0 = unlimited) |
| Include full release text | Fetch each detail page for full body, summary and document links (slower) |
| Advanced — custom User-Agent | Override the default SEC.gov User-Agent (optional) |
### Output
Each row looks like this (you can download the dataset as JSON, HTML, CSV, or Excel):
```json
{
"releaseType": "litigation_release",
"releaseTypeLabel": "Litigation Release",
"releaseNumber": "LR-26568",
"date": "2026-06-16",
"dateTime": "2026-06-16T14:02:03Z",
"respondents": "Bruce Cameron Conway",
"fileNumber": null,
"commentsDue": null,
"seeAlso": "Consent of Defendant, Final Judgment",
"detailUrl": "https://www.sec.gov/enforcement-litigation/litigation-releases/lr-26568",
"documentUrls": [
"https://www.sec.gov/files/litigation/litreleases/2026/cons26568.pdf",
"https://www.sec.gov/files/litigation/litreleases/2026/judg26568.pdf"
],
"source": "SEC Enforcement & Litigation (public domain, sec.gov)",
"scrapedAt": "2026-06-18T17:45:07.179Z"
}
````
`fileNumber` and `commentsDue` are populated for administrative proceedings (they don't exist for litigation releases, so they're `null` there). With **Include full release text** on, rows also carry `summary` and `fullText`.
### Data table
| Field | Description |
|---|---|
| releaseType / releaseTypeLabel | `litigation_release`, `administrative_proceeding`, or `aaer` |
| releaseNumber | SEC release number (e.g. `LR-26568`, `34-105730`, `AAER-4593`) |
| date / dateTime | Publication date (YYYY-MM-DD) and full ISO timestamp |
| respondents | Defendants / respondents named in the release |
| fileNumber | SEC file number (administrative proceedings, e.g. `3-22327`) |
| commentsDue | Comment deadline, when applicable |
| seeAlso | "See also" label(s) on the release (e.g. consent, final judgment) |
| detailUrl | Link to the release detail page (HTML) or document (PDF) |
| documentUrls | All linked case documents — complaints, orders, judgments (PDF). Empty if none |
| summary / fullText | Body text + summary (only with *Include full release text*) |
### How much does it cost to scrape SEC enforcement actions?
The actor reads free, public government web pages, so runs are fast and cheap — a typical filtered run of a few hundred releases costs a small fraction of a compute unit. Leaving **Include full release text** off keeps runs lean (one request per page of ~100 releases). Turning it on adds one request per release, so use a tight **Date range** or **Max results** to control cost. The free tier is enough to evaluate the actor and run small daily alerts.
### Tips & advanced options
- **Daily enforcement alerts:** schedule a run with `Date range = Last 24 hours` and your keyword filters.
- **Screen a company/person:** set a wide date range (e.g. *All time*) and a **Keyword** with the name — but raise **Max results**, since keyword filtering scans the archive newest-first.
- **Keep it lean:** leave **Include full release text** off unless you need the body — it makes runs slower and larger.
- **Combine feeds:** pair with our **SEC EDGAR Financials** actor to link enforcement targets to their filings for a full "SEC intelligence" picture.
### FAQ, disclaimers & support
- **Is this legal?** The actor only retrieves publicly available pages from the SEC's official website. U.S. government works (including SEC enforcement releases) are in the **public domain**. This actor and its author are **not affiliated with or endorsed by the SEC**.
- **Personal data:** defendant/respondent names are part of public enforcement records published by the SEC itself. Use them in compliance with applicable laws for legitimate research, compliance, journalism and due-diligence purposes.
- **Accuracy:** data mirrors what the SEC publishes; always confirm against the linked official release before relying on it for legal or investment decisions.
- **Limitations:** the SEC list view has no working free-text search, so keyword filtering is applied client-side over the selected date range. Full text is available only for HTML detail pages; some releases link directly to a PDF (captured as `documentUrl`).
- **Support & custom work:** found a bug or need an extra field or source (FTC, DOJ, state regulators)? Open an issue on the Issues tab — feedback and custom-solution requests are welcome.
### Changelog
#### 0.1 (2026-06-18)
- Initial release: Litigation Releases, Administrative Proceedings and AAER feeds; release-type/keyword/date filters; optional full-text enrichment; defendants, release/file numbers and document links.
- Consolidated all case-document links into a single `documentUrls` array (populated across every release type) and cleaned up the output schema.
***
### More foXLabs data tools
This Actor is part of the **[foXLabs data platform](https://data.foxlabs.com.tr/)** — a suite of public-data scrapers for company intelligence, procurement, financial and AI-search visibility data. Browse the full Actor suite and free how-to guides at **[data.foxlabs.com.tr](https://data.foxlabs.com.tr/)**.
# Actor input Schema
## `releaseTypes` (type: `array`):
Which SEC enforcement feeds to pull. Leave empty for all three. Litigation Releases = civil court actions. Administrative Proceedings = SEC in-house orders. AAER = accounting & auditing enforcement.
## `searchTerm` (type: `string`):
Optional filter matched against the defendant/respondent names and release/file numbers within the selected date range (e.g. a company or person, 'Tesla', 'Coinbase', 'LR-26568'). Case-insensitive substring match. Widen the date range to search further back. Leave empty to list everything.
## `datePreset` (type: `string`):
Quick filter on the release publication date. Pick 'Custom' to use the From/To fields. Choose 'All time' to crawl the full archive (back to the 1990s).
## `dateFrom` (type: `string`):
YYYY-MM-DD (e.g. 2026-01-01). Only used when Date range = Custom.
## `dateTo` (type: `string`):
YYYY-MM-DD. Only used when Date range = Custom. Leave empty for 'today'.
## `maxResults` (type: `integer`):
Hard cap on dataset rows (across all selected release types). Helps control cost and runtime. Set to 0 for unlimited.
## `includeFullText` (type: `boolean`):
Fetch each release's detail page and add the full body text, a short summary and linked complaint/order documents. Slower and pricier (one extra request per release). Works for HTML detail pages; PDF-only releases just keep their document link.
## `userAgent` (type: `string`):
SEC.gov requires a descriptive User-Agent. A sensible default is used; override only if you have a reason (e.g. include your own contact email).
## Actor input object example
```json
{
"releaseTypes": [],
"datePreset": "last_30_days",
"maxResults": 500,
"includeFullText": false
}
```
# Actor output Schema
## `dataset` (type: `string`):
No description
# 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 '' with your token
const client = new ApifyClient({
token: '',
});
// Prepare Actor input
const input = {
"releaseTypes": []
};
// Run the Actor and wait for it to finish
const run = await client.actor("foxlabs/sec-enforcement-actions").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 '' with your token.
client = ApifyClient("")
# Prepare the Actor input
run_input = { "releaseTypes": [] }
# Run the Actor and wait for it to finish
run = client.actor("foxlabs/sec-enforcement-actions").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 '{
"releaseTypes": []
}' |
apify call foxlabs/sec-enforcement-actions --silent --output-dataset
```
## MCP server setup
```json
{
"mcpServers": {
"apify": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.apify.com/?tools=foxlabs/sec-enforcement-actions",
"--header",
"Authorization: Bearer "
]
}
}
}
```
## OpenAPI specification
```json
{
"openapi": "3.0.1",
"info": {
"title": "SEC Enforcement Tracker — Litigation, Proceedings & AAER",
"description": "Official SEC.gov enforcement feed: litigation releases, administrative proceedings and accounting & auditing enforcement (AAER). Filter by type, keyword, date. Defendants, release/file numbers, complaint links. Regulatory intel for compliance, securities lawyers, journalists.",
"version": "0.1",
"x-build-id": "WFJAgdtVdfudG1kpJ"
},
"servers": [
{
"url": "https://api.apify.com/v2"
}
],
"paths": {
"/acts/foxlabs~sec-enforcement-actions/run-sync-get-dataset-items": {
"post": {
"operationId": "run-sync-get-dataset-items-foxlabs-sec-enforcement-actions",
"x-openai-isConsequential": false,
"summary": "Executes an Actor, waits for its completion, and returns Actor's dataset items in response.",
"tags": [
"Run Actor"
],
"requestBody": {
"required": true,
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/inputSchema"
}
}
}
},
"parameters": [
{
"name": "token",
"in": "query",
"required": true,
"schema": {
"type": "string"
},
"description": "Enter your Apify token here"
}
],
"responses": {
"200": {
"description": "OK"
}
}
}
},
"/acts/foxlabs~sec-enforcement-actions/runs": {
"post": {
"operationId": "runs-sync-foxlabs-sec-enforcement-actions",
"x-openai-isConsequential": false,
"summary": "Executes an Actor and returns information about the initiated run in response.",
"tags": [
"Run Actor"
],
"requestBody": {
"required": true,
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/inputSchema"
}
}
}
},
"parameters": [
{
"name": "token",
"in": "query",
"required": true,
"schema": {
"type": "string"
},
"description": "Enter your Apify token here"
}
],
"responses": {
"200": {
"description": "OK",
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/runsResponseSchema"
}
}
}
}
}
}
},
"/acts/foxlabs~sec-enforcement-actions/run-sync": {
"post": {
"operationId": "run-sync-foxlabs-sec-enforcement-actions",
"x-openai-isConsequential": false,
"summary": "Executes an Actor, waits for completion, and returns the OUTPUT from Key-value store in response.",
"tags": [
"Run Actor"
],
"requestBody": {
"required": true,
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/inputSchema"
}
}
}
},
"parameters": [
{
"name": "token",
"in": "query",
"required": true,
"schema": {
"type": "string"
},
"description": "Enter your Apify token here"
}
],
"responses": {
"200": {
"description": "OK"
}
}
}
}
},
"components": {
"schemas": {
"inputSchema": {
"type": "object",
"properties": {
"releaseTypes": {
"title": "Release types",
"type": "array",
"description": "Which SEC enforcement feeds to pull. Leave empty for all three. Litigation Releases = civil court actions. Administrative Proceedings = SEC in-house orders. AAER = accounting & auditing enforcement.",
"items": {
"type": "string",
"enum": [
"litigation_release",
"administrative_proceeding",
"aaer"
],
"enumTitles": [
"Litigation Releases (civil court)",
"Administrative Proceedings (in-house)",
"Accounting & Auditing Enforcement (AAER)"
]
},
"default": []
},
"searchTerm": {
"title": "Keyword (defendant / respondent name)",
"type": "string",
"description": "Optional filter matched against the defendant/respondent names and release/file numbers within the selected date range (e.g. a company or person, 'Tesla', 'Coinbase', 'LR-26568'). Case-insensitive substring match. Widen the date range to search further back. Leave empty to list everything."
},
"datePreset": {
"title": "Date range (by release date)",
"enum": [
"last_24_hours",
"last_7_days",
"last_30_days",
"last_90_days",
"last_year",
"ytd",
"all_time",
"custom"
],
"type": "string",
"description": "Quick filter on the release publication date. Pick 'Custom' to use the From/To fields. Choose 'All time' to crawl the full archive (back to the 1990s).",
"default": "last_30_days"
},
"dateFrom": {
"title": "Custom from date",
"pattern": "^[0-9]{4}-[0-9]{2}-[0-9]{2}$",
"type": "string",
"description": "YYYY-MM-DD (e.g. 2026-01-01). Only used when Date range = Custom."
},
"dateTo": {
"title": "Custom to date",
"pattern": "^[0-9]{4}-[0-9]{2}-[0-9]{2}$",
"type": "string",
"description": "YYYY-MM-DD. Only used when Date range = Custom. Leave empty for 'today'."
},
"maxResults": {
"title": "Max results",
"minimum": 0,
"type": "integer",
"description": "Hard cap on dataset rows (across all selected release types). Helps control cost and runtime. Set to 0 for unlimited.",
"default": 500
},
"includeFullText": {
"title": "Include full release text",
"type": "boolean",
"description": "Fetch each release's detail page and add the full body text, a short summary and linked complaint/order documents. Slower and pricier (one extra request per release). Works for HTML detail pages; PDF-only releases just keep their document link.",
"default": false
},
"userAgent": {
"title": "Advanced — custom User-Agent",
"type": "string",
"description": "SEC.gov requires a descriptive User-Agent. A sensible default is used; override only if you have a reason (e.g. include your own contact email)."
}
}
},
"runsResponseSchema": {
"type": "object",
"properties": {
"data": {
"type": "object",
"properties": {
"id": {
"type": "string"
},
"actId": {
"type": "string"
},
"userId": {
"type": "string"
},
"startedAt": {
"type": "string",
"format": "date-time",
"example": "2025-01-08T00:00:00.000Z"
},
"finishedAt": {
"type": "string",
"format": "date-time",
"example": "2025-01-08T00:00:00.000Z"
},
"status": {
"type": "string",
"example": "READY"
},
"meta": {
"type": "object",
"properties": {
"origin": {
"type": "string",
"example": "API"
},
"userAgent": {
"type": "string"
}
}
},
"stats": {
"type": "object",
"properties": {
"inputBodyLen": {
"type": "integer",
"example": 2000
},
"rebootCount": {
"type": "integer",
"example": 0
},
"restartCount": {
"type": "integer",
"example": 0
},
"resurrectCount": {
"type": "integer",
"example": 0
},
"computeUnits": {
"type": "integer",
"example": 0
}
}
},
"options": {
"type": "object",
"properties": {
"build": {
"type": "string",
"example": "latest"
},
"timeoutSecs": {
"type": "integer",
"example": 300
},
"memoryMbytes": {
"type": "integer",
"example": 1024
},
"diskMbytes": {
"type": "integer",
"example": 2048
}
}
},
"buildId": {
"type": "string"
},
"defaultKeyValueStoreId": {
"type": "string"
},
"defaultDatasetId": {
"type": "string"
},
"defaultRequestQueueId": {
"type": "string"
},
"buildNumber": {
"type": "string",
"example": "1.0.0"
},
"containerUrl": {
"type": "string"
},
"usage": {
"type": "object",
"properties": {
"ACTOR_COMPUTE_UNITS": {
"type": "integer",
"example": 0
},
"DATASET_READS": {
"type": "integer",
"example": 0
},
"DATASET_WRITES": {
"type": "integer",
"example": 0
},
"KEY_VALUE_STORE_READS": {
"type": "integer",
"example": 0
},
"KEY_VALUE_STORE_WRITES": {
"type": "integer",
"example": 1
},
"KEY_VALUE_STORE_LISTS": {
"type": "integer",
"example": 0
},
"REQUEST_QUEUE_READS": {
"type": "integer",
"example": 0
},
"REQUEST_QUEUE_WRITES": {
"type": "integer",
"example": 0
},
"DATA_TRANSFER_INTERNAL_GBYTES": {
"type": "integer",
"example": 0
},
"DATA_TRANSFER_EXTERNAL_GBYTES": {
"type": "integer",
"example": 0
},
"PROXY_RESIDENTIAL_TRANSFER_GBYTES": {
"type": "integer",
"example": 0
},
"PROXY_SERPS": {
"type": "integer",
"example": 0
}
}
},
"usageTotalUsd": {
"type": "number",
"example": 0.00005
},
"usageUsd": {
"type": "object",
"properties": {
"ACTOR_COMPUTE_UNITS": {
"type": "integer",
"example": 0
},
"DATASET_READS": {
"type": "integer",
"example": 0
},
"DATASET_WRITES": {
"type": "integer",
"example": 0
},
"KEY_VALUE_STORE_READS": {
"type": "integer",
"example": 0
},
"KEY_VALUE_STORE_WRITES": {
"type": "number",
"example": 0.00005
},
"KEY_VALUE_STORE_LISTS": {
"type": "integer",
"example": 0
},
"REQUEST_QUEUE_READS": {
"type": "integer",
"example": 0
},
"REQUEST_QUEUE_WRITES": {
"type": "integer",
"example": 0
},
"DATA_TRANSFER_INTERNAL_GBYTES": {
"type": "integer",
"example": 0
},
"DATA_TRANSFER_EXTERNAL_GBYTES": {
"type": "integer",
"example": 0
},
"PROXY_RESIDENTIAL_TRANSFER_GBYTES": {
"type": "integer",
"example": 0
},
"PROXY_SERPS": {
"type": "integer",
"example": 0
}
}
}
}
}
}
}
}
}
}
```