# SEC EDGAR Full-Text Search: Filings by Keyword and Form (`accountable_eel/sec-edgar-full-text-search-lookup`) Actor

Search the full text of SEC EDGAR filings by keyword or phrase, form type and date. One row per filing with company, form, filing date and a link to the matching document, plus an alert mode that only returns new filings.

- **URL**: https://apify.com/accountable_eel/sec-edgar-full-text-search-lookup.md
- **Developed by:** [Adriana Voss](https://apify.com/accountable_eel) (community)
- **Categories:** Lead generation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.50 / 1,000 sec filing matcheds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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: Filings by Keyword and Form

**Search the full text of SEC filings for a word or phrase, filtered by form type and date, and get one row per filing.**
Each row has the company, CIK, form, filing date, period, and a link to the matching document on sec.gov. Use it to find every 10-K that mentions "going concern", every 8-K about a "cybersecurity incident", or every filing that names a supplier. Turn on monitoring and run it on a schedule to get only filings that are new since your last run, charged per filing and free on a quiet day.

**Who uses it:** analysts and screeners watching risk language, compliance and due-diligence teams, journalists, and agents that need "which filings say X" as structured rows.

**Related actors:** for one company's filing list use [SEC EDGAR Company Lookup](https://apify.com/accountable_eel/sec-edgar-company-lookup); for 8-K events by item number use [SEC 8-K Event Alerts](https://apify.com/accountable_eel/sec-8k-event-alerts). This actor searches what filings *say*, across all companies.

### How to use

1. **In the Apify Console.** Open the actor page and click **Start** — the `queries` field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. **Via the API.** Call it directly with a POST request — no Console needed once you have an API token:
   ```bash
   curl "https://api.apify.com/v2/acts/accountable_eel~sec-edgar-full-text-search-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"queries":["going concern"]}'
   ```
3. **On a schedule.** Save this actor as an Apify **Task** with the input you want, then add a **Schedule** (hourly, daily, weekly) so it runs on its own — no server of your own required.

### Input

```json
{
  "queries": [
    "going concern"
  ]
}
```

One word or phrase per line, matched against the full text of SEC filings and their exhibits. Put a phrase in double quotes for an exact match. Each line is a separate search; a filing that matches several is returned once. Accepted formats: going concern, "material weakness", "cybersecurity incident".

Searching form `10-K` also returns its amendments (`10-K/A`). Quote a phrase for an exact match. Several lines are separate searches; a filing that matches more than one comes back once, with `matchedQueries` listing which. The index holds one hit per document, so a 10-K and its exhibits are merged into a single filing row (`matchedDocuments` says how many matched).

### Output

One row per filing, for example:

| query | found | status | searchSummary | filingCount | truncated | monitorStatus | filings | accessionNumber | companyName | ticker | cik | form | filedAt | periodEnding | documentType | fileDescription | sicCode | businessLocation | incorporationState | matchedDocuments | matchedQueries | documentUrl | filingIndexUrl | isNew | firstSeenAt | scrapedAt |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| going concern | true | OK | <search run> | <filings returned> | <more results were available> | <monitoring status> | \<all filings (full list)> | <accession number> | <company> | <ticker> | <cik> | <form> | <filed on> | <period ending> | <matched document type> | <document description> | <sic code> | <business location> | <state of incorporation> | <matching documents> | <matched phrases> | <filing document> | <filing index> | \<is this filing new?> | <first seen on a run> | 1970-01-01T00:00:00.000Z |

A search with no match comes back as one row with `"found": false` and is never charged. Fields SEC does not publish for a filing (for example `periodEnding` on most 8-Ks) are `null`, never `0` or an empty string.

Only filings in SEC EDGAR full-text search coverage are searchable; SEC publishes it from 2001 onward.

### Pricing

Pay-per-event. A flat per-run fee covers session/proxy warmup; you're billed
per item only when data is actually found and returned — see
`.actor/pay_per_event.json` for exact prices. A miss is never charged.

### Example runs

Paste any of these into the Input tab and press Start. All three return rows with no key, no token
and no account of your own beyond an Apify login.

**10-Ks that mention "going concern", last 30 days.** The default shape.

```json
{
  "queries": ["going concern"],
  "forms": ["10-K"],
  "sinceDays": 30,
  "maxResults": 20
}
```

**8-Ks about a cybersecurity incident in a fixed window.**

```json
{
  "queries": ["\"cybersecurity incident\""],
  "forms": ["8-K"],
  "startDate": "2026-09-01",
  "endDate": "2026-10-11",
  "maxResults": 50
}
```

**Material weakness language across 10-K and 10-Q, with monitoring on.**

```json
{
  "queries": ["\"material weakness\""],
  "forms": ["10-K", "10-Q"],
  "sinceDays": 7,
  "onlyNewSinceLastRun": true
}
```

### Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

```bash
curl "https://api.apify.com/v2/acts/accountable_eel~sec-edgar-full-text-search-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"queries":["going concern"]}'
```

**n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~sec-edgar-full-text-search-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body Content Type `JSON`, JSON Body `{"queries":["going concern"]}` (swap in an expression from an earlier node for a real value).

**Clay.** Add an "HTTP API" column: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~sec-edgar-full-text-search-lookup/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body `{"queries":["{{search}}"]}`, mapping the row's search into the `queries` array.

**MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "sec edgar full text search" — the agent will find and run this actor.

# Actor input Schema

## `queries` (type: `array`):

One word or phrase per line, matched against the full text of SEC filings and their exhibits. Put a phrase in double quotes for an exact match. Each line is a separate search; a filing that matches several is returned once. Accepted formats: going concern, "material weakness", "cybersecurity incident". You're only charged for the ones we actually find — a miss costs nothing.

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

Optional. Only filings of these form types, for example 10-K, 10-Q, 8-K, S-1, 20-F. Leave empty for every form.

## `testRun` (type: `boolean`):

Turn this on to test your input on a small sample before running the full list. Turn it off to process everything.

## `onlyFound` (type: `boolean`):

Only keep rows where something was actually found. Misses are always free, whether or not you show them here.

## `includeKeywords` (type: `array`):

Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything.

## `excludeKeywords` (type: `array`):

Optional. Drop any result that mentions one of these words. Leave empty to skip nothing.

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

Up to 500. Caps how many filings you get (and pay for) in one run.

## `sinceDays` (type: `integer`):

The search window ends today and starts this many days back. Ignored when you set a start date.

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

Optional, YYYY-MM-DD. Overrides the last-N-days window.

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

Optional, YYYY-MM-DD. Defaults to today.

## `onlyNewSinceLastRun` (type: `boolean`):

On: only filings not returned by your earlier runs are returned and charged for — run this on a schedule as a filing alert. Off: every matching filing is returned every time.

## `deltaName` (type: `string`):

Optional. Name this search's monitoring memory so you can tell two schedules of this actor apart, or keep one memory across an input change. Leave empty to auto-derive one from your filters.

## `columns` (type: `array`):

Choose which pieces of information to include in each result row. All are included by default.

## `expandRows` (type: `boolean`):

When on, each filing found gets its own row instead of being grouped under its search. You're still only charged once per search, no matter how many rows it produces.

## `maxConcurrency` (type: `integer`):

Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady.

## Actor input object example

```json
{
  "queries": [
    "going concern"
  ],
  "forms": [
    "10-K"
  ],
  "testRun": false,
  "onlyFound": false,
  "includeKeywords": [],
  "excludeKeywords": [],
  "maxResults": 100,
  "sinceDays": 30,
  "startDate": "",
  "endDate": "",
  "onlyNewSinceLastRun": false,
  "deltaName": "",
  "columns": [
    "searchSummary",
    "filingCount",
    "truncated",
    "monitorStatus",
    "filings",
    "accessionNumber",
    "companyName",
    "ticker",
    "cik",
    "form",
    "filedAt",
    "periodEnding",
    "documentType",
    "fileDescription",
    "sicCode",
    "businessLocation",
    "incorporationState",
    "matchedDocuments",
    "matchedQueries",
    "documentUrl",
    "filingIndexUrl",
    "isNew",
    "firstSeenAt"
  ],
  "expandRows": true,
  "maxConcurrency": 1
}
```

# Actor output Schema

## `results` (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 = {
    "queries": [
        "going concern"
    ],
    "forms": [
        "10-K"
    ],
    "includeKeywords": [],
    "excludeKeywords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/sec-edgar-full-text-search-lookup").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 = {
    "queries": ["going concern"],
    "forms": ["10-K"],
    "includeKeywords": [],
    "excludeKeywords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/sec-edgar-full-text-search-lookup").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 '{
  "queries": [
    "going concern"
  ],
  "forms": [
    "10-K"
  ],
  "includeKeywords": [],
  "excludeKeywords": []
}' |
apify call accountable_eel/sec-edgar-full-text-search-lookup --silent --output-dataset

```

## MCP server setup

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

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/1LwCMg2GPguLx9Ner/builds/FceSe5XYUC1eXkldB/openapi.json