# SEC EDGAR Full-Text Search Scraper (`integraiia/sec-edgar-search`) Actor

Search every SEC filing since 2001 by phrase, form type and date range through EDGAR's official full-text search, and get structured filing records with direct document links, filer names, tickers, CIKs, SIC codes and 8-K items. Pay per filing.

- **URL**: https://apify.com/integraiia/sec-edgar-search.md
- **Developed by:** [Will Vasquez](https://apify.com/integraiia) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.10 / 1,000 sec filing documents

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/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 EDGAR Full-Text Search Scraper

Searches the full text of every SEC filing since 2001 through EDGAR's official full-text search (the same engine behind efts.sec.gov) and returns one structured record per matching document: direct document URL, filing index URL, form type, document type, filing date, period, every filer with name, ticker and CIK, SIC codes, business locations, states of incorporation, 8-K item numbers and file numbers. Phrase search, form-type filter and date range. Official U.S. government data, no login, no proxies. Pay per filing document.

### What it returns

One record per matching document:

| Field | Meaning |
|---|---|
| `adsh` | Accession number of the filing |
| `fileName`, `documentUrl` | The matching document inside the filing |
| `filingIndexUrl` | The filing's index page listing all its documents |
| `form`, `rootForms` | Form type (e.g. 8-K) and the root form(s) |
| `fileType`, `fileDescription` | Document type, e.g. EX-99.1 |
| `fileDate`, `periodEnding` | Filing date and period |
| `ciks`, `entities` | Filers: `{ name, ticker, cik }` |
| `sics`, `bizLocations`, `bizStates`, `incStates` | Industry and location codes |
| `items` | 8-K item numbers, e.g. 2.02 |
| `fileNumbers`, `filmNumbers` | SEC file and film numbers |
| `query` | The search that produced the record |

### Input

- `query` — the phrase or terms to search, same syntax as efts.sec.gov (quotes for exact phrases).
- `forms` — optional form types to keep (8-K, 10-K, 10-Q, S-1, DEF 14A, ...).
- `startDate`, `endDate` — optional filing date range (YYYY-MM-DD).
- `maxItems` — stop after this many documents (default 100, max 10,000).

### Output sample

```json
{
  "adsh": "0000091142-26-000005",
  "fileName": "a12312025exhibit991.htm",
  "documentUrl": "https://www.sec.gov/Archives/edgar/data/91142/000009114226000005/a12312025exhibit991.htm",
  "filingIndexUrl": "https://www.sec.gov/Archives/edgar/data/91142/000009114226000005/0000091142-26-000005-index.htm",
  "form": "8-K",
  "fileType": "EX-99.1",
  "fileDate": "2026-01-29",
  "entities": [{ "name": "SMITH A O CORP", "ticker": "AOS", "cik": "0000091142" }],
  "sics": ["3630"],
  "items": ["2.02", "9.01"]
}
```

### Pricing

Pay per filing document. You are charged one `filing` event for each record written to the dataset, nothing for searches with no hits.

### Limits

- Follows the SEC's fair-access rules: an identified User-Agent with a contact address and well under 10 requests per second.
- EDGAR full-text search covers filings from 2001 onward and returns up to 100 hits per page; the Actor pages until `maxItems`.

# Actor input Schema

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

What to search for in filing text. Use quotes for exact phrases, e.g. "supply chain disruption". Same syntax as efts.sec.gov.

## `forms` (type: `array`):

Optional list of form types to keep, e.g. 8-K, 10-K, 10-Q, S-1, DEF 14A.

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

Optional, YYYY-MM-DD. Filing date range start.

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

Optional, YYYY-MM-DD. Filing date range end.

## `maxItems` (type: `integer`):

Stop after this many filing documents. Each one is one paid event. Default 100, maximum 10,000.

## Actor input object example

```json
{
  "query": "\"water heater\"",
  "maxItems": 100
}
```

# Actor output Schema

## `filings` (type: `string`):

All matching filing documents as JSON (one record per document).

# 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": "\"water heater\""
};

// Run the Actor and wait for it to finish
const run = await client.actor("integraiia/sec-edgar-search").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": "\"water heater\"" }

# Run the Actor and wait for it to finish
run = client.actor("integraiia/sec-edgar-search").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": "\\"water heater\\""
}' |
apify call integraiia/sec-edgar-search --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,integraiia/sec-edgar-search"
        }
    }
}
```

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/ldBHtFvUbQdR8bFM6/builds/OZ2kBGKZv2V9eQkr2/openapi.json