# Regulatory Filing Notifications Scraper (`datapilot/regulatory-filing-notifications-scraper`) Actor

Search 8-K, 10-K, 10-Q, S-1, DEF 14A, SC 13D, and SC 13G filings from the last 7 days. Extract filing ID, company, form type, date, CIK, description, and direct SEC filing URL.upports multiple keywords, pagination, retries, and Residential Proxy.

- **URL**: https://apify.com/datapilot/regulatory-filing-notifications-scraper.md
- **Developed by:** [Data Pilot](https://apify.com/datapilot) (community)
- **Categories:** Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 scraped results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#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

📜 **Regulatory Filing Notifications** Scraper is a powerful Apify Actor designed to discover, track, and collect newly filed SEC disclosures directly from the SEC's own EDGAR Full-Text Search API. This tool provides comprehensive **Regulatory Filing Notifications** intelligence including filing ID, entity name, form type, file date, CIK, and a direct link to the filing document for any keyword. Whether you're building a compliance monitoring dashboard, tracking industry disclosure activity, or conducting financial research, the Regulatory Filing Notifications Scraper delivers actionable **Regulatory Filing Notifications** insights efficiently.

With retry-resilient EDGAR API querying, keyword-based full-text search, automatic pagination, and reliable Apify Dataset delivery, the Regulatory Filing Notifications Scraper ensures comprehensive **Regulatory Filing Notifications** coverage across any list of search keywords. It focuses on key **Regulatory Filing Notifications** signals including form type, filer entity, and filing date, making it an essential tool for compliance monitoring and regulatory intelligence.

***

### 📋 Table of Contents

- [Features](#-features)
- [Data Source](#-data-source)
- [How It Works](#-how-it-works)
- [Input](#-input)
- [Output](#-output)
- [Technical Stack](#-technical-stack)
- [Data Fields](#-data-fields-explained)
- [Use Cases](#-use-cases)
- [Quick Start](#-quick-start)
- [Configuration](#-configuration)
- [Performance](#-performance)
- [Important Notes](#-important-notes)
- [License & Legal](#-license--legal)

***

### 🔥 Features

- **Direct EDGAR API Access** – Queries the SEC's official Full-Text Search API (`efts.sec.gov`) directly for fast, structured **Regulatory Filing Notifications** data.
- **Multi-Keyword Search** – Accepts any number of search keywords and scans recent filings for each.
- **Configurable Form Coverage** – Searches across major form types by default: 8-K, 10-K, 10-Q, S-1, DEF 14A, SC 13D, and SC 13G.
- **Rolling Date Window** – Automatically searches the most recent 7-day filing window from the SEC's live index.
- **Automatic Pagination** – Pages through all available results for a keyword up to the configured maximum.
- **Retry-Resilient Requests** – Automatically retries on rate limits (429) and auth errors (401/403) with backoff delays.
- **CIK & Filing URL Resolution** – Extracts the filer's CIK number and builds a direct link to the filing document on EDGAR.
- **Residential Proxy Support** – Apify residential proxy for reliable **Regulatory Filing Notifications** access.
- **Incremental Dataset Push** – Pushes each batch of results to the Dataset as it's collected, not just at the end.
- **Graceful Error Handling** – Skips a failing page or keyword without stopping the whole run.

***

### 📊 Data Source

#### **SEC EDGAR Full-Text Search API**

- **Authority**: The U.S. Securities and Exchange Commission's official EDGAR Full-Text Search index (`efts.sec.gov/LATEST/search-index`)
- **Access Method**: Browser-impersonated HTTP requests via `curl_cffi`, run through an executor for async compatibility
- **Coverage**: Any publicly filed **Regulatory Filing Notifications** document matching the given keyword within the configured date range
- **Data**: Structured JSON search hits, including filer identity, form type, and filing metadata
- **Access**: Public API, no API key required (SEC requests a descriptive User-Agent, which is included)
- **Update Frequency**: Reflects EDGAR's current live filing index at time of run

***

### ⚙️ How It Works

The Regulatory Filing Notifications Scraper accepts a list of search keywords and queries the SEC EDGAR Full-Text Search API for each, restricted to a rolling 7-day date window and a fixed set of common form types. For each keyword, the Actor pages through all available results, retrying automatically on rate limits or transient auth errors with increasing backoff delays. Every search hit is normalized into a clean record, extracting the filer's CIK, entity name, form type, file date, and constructing a direct link to the filing document on SEC EDGAR. Results are pushed to the Apify Dataset incrementally, batch by batch, as they're collected across all keywords.

**Key Processing Steps:**

1. **Input Parsing** – Accept a list of keywords (or a single keyword) to search for
2. **Proxy Setup** – Configure Apify residential proxy for the impersonated HTTP session
3. **Date Window Calculation** – Compute the rolling 7-day search window ending today
4. **Keyword Loop** – Iterate through each **Regulatory Filing Notifications** search keyword
5. **Search Request** – Query EDGAR's full-text search API with the keyword, forms, and date range
6. **Retry Handling** – Back off and retry on rate limits (429) or auth errors (401/403)
7. **Hit Normalization** – Extract filing ID, entity, form type, file date, CIK, and build the filing URL
8. **Pagination** – Continue requesting subsequent pages until all available results are collected
9. **Incremental Push** – Push each batch of normalized results to the Dataset as it's ready
10. **Rate Limiting** – Apply a short delay between paginated requests

**Key Benefits:**

- Pull **Regulatory Filing Notifications** for any keyword without manually searching EDGAR
- Catch newly filed disclosures within a rolling weekly window
- Monitor multiple keywords or topics in a single run
- Feed compliance dashboards, investor research pipelines, or watchdog tools
- Automate recurring **Regulatory Filing Notifications** checks as new filings are published

***

### 📥 Input

The Actor accepts the following input parameters:

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `keywords` | array | `["climate"]` | List of search terms to scan for matching **Regulatory Filing Notifications**. |
| `keyword` | string | `"climate"` | Optional single keyword, used if `keywords` is not provided. |
| `proxyConfiguration` | object | `{"useApifyProxy": true, "apifyProxyGroups": ["RESIDENTIAL"]}` | Apify proxy configuration for the search session. |

**Example Input:**

```json
{
  "keywords": ["climate risk", "data breach", "cybersecurity incident"],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}
```

**Search a Single Keyword:**

```json
{
  "keyword": "merger agreement"
}
```

**Search Multiple Keywords:**

```json
{
  "keywords": ["stock buyback", "executive compensation"]
}
```

***

### 📤 Output

The Actor pushes **Regulatory Filing Notifications** records with the following structure:

| Field | Type | Description |
|-------|------|-------------|
| `search_keyword` | string | The keyword that matched this **Regulatory Filing Notifications** result |
| `filing_id` | string | The filing's accession number (or internal hit ID as fallback) |
| `title` | string | Form type plus file description, when available |
| `entity` | string | Name(s) of the filer entity |
| `form_type` | string | SEC form type (e.g., "8-K", "10-K", "DEF 14A") |
| `file_date` | string | Date the filing was submitted to EDGAR |
| `filing_url` | string | Direct URL to the filing document on SEC EDGAR |
| `cik` | string | The filer's Central Index Key (CIK) number |
| `scraped_at` | string | ISO 8601 timestamp of when the record was scraped |

**Example Regulatory Filing Notifications Record:**

```json
{
  "search_keyword": "climate risk",
  "filing_id": "0001234567-26-000123",
  "title": "8-K filing - Item 1.01 Entry into a Material Agreement",
  "entity": "Example Energy Corp",
  "form_type": "8-K",
  "file_date": "2026-08-10",
  "filing_url": "https://www.sec.gov/Archives/edgar/data/1234567/000123456726000123/filing.txt",
  "cik": "1234567",
  "scraped_at": "2026-08-11T09:00:00+00:00"
}
```

***

### 🧰 Technical Stack

- **HTTP Client:** `curl_cffi` with Chrome impersonation for reliable access to the SEC EDGAR API
- **Concurrency:** `asyncio` with an executor bridge for running the impersonated client asynchronously
- **Pattern Matching:** `re` for extracting CIK numbers from display names when not directly provided
- **Date Handling:** `datetime` and `timedelta` for computing the rolling search window
- **Proxy:** Apify Proxy with `RESIDENTIAL` configuration by default
- **Logging:** Apify Actor logging system
- **Platform:** Apify Actor serverless environment

***

### 📊 Data Fields Explained

#### **Filing Identity**

- **filing\_id**: The SEC accession number uniquely identifying the filing
- **title**: A human-readable summary combining form type and file description

#### **Filer Details**

- **entity**: The display name(s) of the company or individual who filed
- **cik**: The SEC's Central Index Key identifying the filer

#### **Filing Metadata**

- **form\_type**: The SEC form classification (8-K, 10-K, 10-Q, S-1, DEF 14A, SC 13D, SC 13G)
- **file\_date**: The date the filing was submitted
- **filing\_url**: Direct link to the filing document on EDGAR
- **search\_keyword**: The keyword that surfaced this result, for traceability across multi-keyword runs

***

### 🎯 Use Cases

- **Compliance Monitoring** – Catch newly filed 8-Ks, proxy statements, or ownership disclosures for tracked companies
- **Investor Research** – Monitor disclosure activity around a specific topic or risk factor
- **Competitive Intelligence** – Track competitor filings for material agreements or leadership changes
- **Legal & Regulatory Research** – Search for filings referencing specific regulatory language or events
- **Academic Research** – Study public disclosure trends and language at scale
- **Media Monitoring** – Source primary filing documents for financial journalism

***

### 🚀 Quick Start

#### **1. Prepare Input**

Go to Apify Console and enter:

```json
{
  "keywords": ["climate"]
}
```

#### **2. Run the Actor**

Click **Start**. The Actor will:

- Search EDGAR's full-text index for each keyword within the last 7 days
- Page through all matching results, retrying on rate limits automatically
- Normalize each hit into a clean **Regulatory Filing Notifications** record
- Push batches to the Dataset incrementally as they're collected

#### **3. Monitor Progress**

Console shows:

```
[1/1] Searching filings for: 'climate'
Done! Pushed 34 filings to Dataset.
```

#### **4. View & Download Results**

- **Results Tab**: All **Regulatory Filing Notifications** records
- **Export**: JSON, CSV, Excel, or HTML
- **Filter**: By form type or entity
- **API Access**: Available via the Apify API

***

### ⚙️ Configuration

Single keyword search:

```json
{
  "keyword": "merger agreement"
}
```

Multiple keywords in one run:

```json
{
  "keywords": ["data breach", "cybersecurity incident", "executive compensation"]
}
```

Custom proxy group:

```json
{
  "keywords": ["climate"],
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}
```

***

### 📈 Performance

#### **Processing Speed**

- One or more paginated requests per keyword, depending on total result volume
- 0.5 second delay between paginated requests to stay within SEC's fair-use expectations
- Automatic retry backoff (up to 3 attempts) on rate limits or transient errors

#### **Resource Usage**

- Memory: Low, since no browser instance is launched
- Network: Multiple lightweight JSON requests per keyword, scaling with result volume
- Proxy: One residential proxy tunnel shared across the impersonated session for the run

***

### ⚠️ Important Notes

#### **Legal & Compliance**

- **Fair Use**: Includes a descriptive `User-Agent` per SEC's access guidelines and applies pacing delays between requests
- **Public Data Only**: Retrieves only publicly filed **Regulatory Filing Notifications** already indexed by EDGAR
- **Legal**: Not legal advice — consult qualified professionals before using this data for compliance-sensitive decisions

#### **Data Quality**

- **Freshness**: Limited to the most recent 7-day filing window by default
- **Completeness**: CIK and filing URL resolution depend on what data EDGAR exposes per hit; some fields may be blank
- **Accuracy**: Sourced directly from the SEC's own EDGAR Full-Text Search API
- **Verification**: Cross-check high-stakes filings against the live SEC EDGAR website

#### **Best Practices**

- Update the contact email in the User-Agent header before running in production, per SEC's access guidelines
- Use specific keywords to keep result volume manageable and relevant
- Re-run periodically (e.g., daily) to catch new filings within the rolling 7-day window
- Expect some `cik` values to be blank if a filer's CIK can't be resolved from the response
- Search multiple related keywords in one run to broaden topic coverage

***

### 📄 License & Legal

**Terms of Use:**

- Use for legitimate research, compliance, and investor relations purposes
- Respect the SEC's EDGAR access guidelines, including fair-use request pacing
- Use **Regulatory Filing Notifications** data responsibly and in compliance with applicable laws

**Disclaimer:**
Regulatory Filing Notifications Scraper is provided as-is for research and analytics purposes. Users are responsible for compliance with the SEC's terms and all applicable laws. This is not legal advice.

***

### ⚖️ Regulatory Filing Notifications Excellence

This Actor is optimized for **Regulatory Filing Notifications** research with:

- ✅ Direct, official EDGAR API access — no HTML scraping fragility
- ✅ Retry-resilient requests with automatic backoff
- ✅ Full pagination across all matching results
- ✅ Multi-keyword search in a single run
- ✅ Incremental Dataset push
- ✅ Production-ready code

# Actor input Schema

## `keywords` (type: `array`):

Enter keywords or phrases to search filings for.

## `forms` (type: `string`):

Comma-separated SEC Form types (e.g. 8-K, 10-K, 10-Q).

## `daysBack` (type: `integer`):

Number of days back to search filings for.

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

Maximum number of filings to collect.

## `contactEmail` (type: `string`):

SEC requires a user-agent email address.

## `useApifyProxy` (type: `boolean`):

Use Residential proxy for SEC requests.

## Actor input object example

```json
{
  "keywords": [
    "Tesla"
  ],
  "forms": "8-K,10-K,10-Q,S-1,DEF 14A,SC 13D,SC 13G",
  "daysBack": 7,
  "maxResults": 100,
  "contactEmail": "monitor@example.com",
  "useApifyProxy": true
}
```

# Actor output Schema

## `crawlResults` (type: `string`):

No description

## `filingsTable` (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 '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "keywords": [
        "Tesla"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("datapilot/regulatory-filing-notifications-scraper").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 = { "keywords": ["Tesla"] }

# Run the Actor and wait for it to finish
run = client.actor("datapilot/regulatory-filing-notifications-scraper").call(run_input=run_input)

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

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

```

## CLI example

```bash
echo '{
  "keywords": [
    "Tesla"
  ]
}' |
apify call datapilot/regulatory-filing-notifications-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,datapilot/regulatory-filing-notifications-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

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