# SEC Filing Search — Full-Text EDGAR Scraper (`hichemdev/sec-filings-scraper`) Actor

Search the full text of every SEC EDGAR filing since 2001 and export the matches: company, tickers, CIK, form type, filing and period dates, 8-K item codes, SIC code, state, accession number and direct document links. Filter by form, date range or CIK. No API key.

- **URL**: https://apify.com/hichemdev/sec-filings-scraper.md
- **Developed by:** [Hichem Ben Moussa](https://apify.com/hichemdev) (community)
- **Categories:** Business, Developer tools, News
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 filings

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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## SEC Filing Search — Full-Text EDGAR Filings Scraper

Search the **full text of every SEC EDGAR filing since 2001** and export the matches as structured data — company, tickers, CIK, form type, filing and period dates, 8-K items, SIC code, state of incorporation and a direct link to the document itself.

This is the search behind EDGAR's full-text interface, turned into a dataset. Ask "which companies disclosed a material weakness in their last 10-K?" and get a table instead of a web page.

No API key required.

### What you get

| Field | Description |
|---|---|
| `company` | Filer name, parsed clean |
| `tickers` | Ticker symbols, e.g. `["FITB","FITBI"]` |
| `cik`, `cikPadded` | SEC company ID, both trimmed and zero-padded |
| `allFilers` | Every filer on a multi-filer submission |
| `form`, `rootForm` | Exact form and its base type, e.g. `10-K/A` → `10-K` |
| `fileType`, `fileDescription` | Which document inside the filing matched |
| `filedAt` | Filing date |
| `periodEnding` | Fiscal period the filing covers |
| `items` | 8-K item codes, e.g. `["5.02"]` for an executive change |
| `sic` | Industry classification code |
| `businessState`, `businessLocation`, `incorporatedState` | Where the company operates and is incorporated |
| `accessionNumber`, `fileNumber` | SEC identifiers |
| `relevanceScore` | EDGAR's own match score |
| `documentUrl` | **Direct link to the matching document** |
| `filingIndexUrl` | The full filing's index page |

### Example input

```json
{
  "query": "material weakness",
  "exactPhrase": true,
  "forms": "10-K",
  "startDate": "2026-01-01",
  "maxFilings": 200
}
```

Monitor a theme across 8-Ks:

```json
{
  "query": "artificial intelligence",
  "forms": "8-K",
  "startDate": "2026-01-01",
  "endDate": "2026-06-30"
}
```

Watch specific companies:

```json
{ "query": "going concern", "ciks": ["320193", "1318605"] }
```

### Example output

```json
{
  "company": "FIFTH THIRD BANCORP",
  "tickers": ["FITB", "FITBI", "FITBO", "FITBP"],
  "cik": "35527",
  "form": "10-K",
  "filedAt": "2022-02-25",
  "periodEnding": "2021-12-31",
  "businessState": "OH",
  "businessLocation": "Cincinnati, OH",
  "sic": "6022",
  "accessionNumber": "0000035527-22-000119",
  "documentUrl": "https://www.sec.gov/Archives/edgar/data/35527/000003552722000119/fitbannualreport202110-k.pdf"
}
```

### Who uses this

- **Investment research** — find every company that used a phrase before it became consensus: "supply chain constraints", "AI capex", "stablecoin"
- **Short sellers and credit analysts** — `going concern`, `material weakness`, `restatement` and `covenant breach` as a screen, not a hunch
- **Corporate lawyers** — precedent language across real filings, and who filed it
- **Risk and compliance** — monitor a competitor's or supplier's 8-K items as they are filed
- **Academics and data teams** — build a labelled filing corpus with document URLs to fetch
- **M\&A and BD teams** — 8-K item codes surface executive changes, acquisitions and material agreements the day they publish

A common setup is a daily run with `startDate` set to yesterday and a watchlist phrase, feeding a webhook.

### Two limits, stated plainly

- **Full-text search starts in 2001.** Older filings exist in EDGAR but are not in the full-text index, so a phrase search cannot reach them. For pre-2001 work you need the filing archives directly, not this search.
- **EDGAR serves at most 10,000 results per query.** It is an OpenSearch index with a hard result window. When your query matches more, the actor reports the true total and tells you it can only retrieve the first 10,000 — the fix is to narrow by form type or split the date range into chunks and run each.

There is a third quirk worth knowing if you ever call this API yourself: **when you exceed the result window, EDGAR replies with HTTP 200 and an error body rather than an error status.** A naive client reads that as success and silently returns nothing. This actor detects it and says what happened.

### The contact e-mail field

The SEC requires automated clients to identify themselves with a contact address and throttles or blocks generic agents. The actor always sends one, but putting **your own e-mail** in the *Contact e-mail* field identifies your runs properly and makes them more reliable — recommended for anything beyond a quick test.

### Pricing

Pay per result. Each matching filing document counts as one result.

### Notes

- One filing can match on several documents; each matching document is its own row, identified by `fileName`, with `accessionNumber` shared. Deduplicate on `accessionNumber` if you want one row per filing.
- `exactPhrase` wraps your query in quotes, which is how EDGAR distinguishes a phrase from loose terms. Turn it off for broader recall.
- This is an unofficial actor and is not affiliated with the SEC.

# Actor input Schema

## `query` (type: `string`):

Words to find in the filing text, e.g. going concern, material weakness, artificial intelligence.

## `exactPhrase` (type: `boolean`):

On, the phrase must appear exactly as written. Off, EDGAR matches the words more loosely.

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

Comma-separated form types, e.g. 10-K or 8-K,10-Q. Leave empty for all forms.

## `ciks` (type: `array`):

Restrict the search to these SEC CIK numbers. Leading zeros are added for you.

## `startDate` (type: `string`):

YYYY-MM-DD. Full-text search covers 2001 onwards.

## `endDate` (type: `string`):

YYYY-MM-DD.

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

The SEC requires API clients to identify themselves and throttles or blocks generic agents. Supplying your own e-mail makes runs more reliable.

## `maxFilings` (type: `integer`):

Stop after this many filings. EDGAR serves at most 10,000 results per query.

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

Optional. A proxy is not required for this actor.

## Actor input object example

```json
{
  "query": "material weakness",
  "exactPhrase": true,
  "forms": "10-K",
  "maxFilings": 50,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

All scraped items as JSON.

## `overview` (type: `string`):

Browse results in the Apify Console.

# 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 = {
    "query": "material weakness",
    "forms": "10-K",
    "maxFilings": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("hichemdev/sec-filings-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 = {
    "query": "material weakness",
    "forms": "10-K",
    "maxFilings": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("hichemdev/sec-filings-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 '{
  "query": "material weakness",
  "forms": "10-K",
  "maxFilings": 50
}' |
apify call hichemdev/sec-filings-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,hichemdev/sec-filings-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/aPxd2rx4G1GV0RBJf/builds/yq7SJ4VWKWMRoJUgT/openapi.json