# SEC 8-K Event Signals: Cyber, Exec Changes, M\&A (`tendoyo/sec-8k-event-signals`) Actor

Real-time feed of material corporate events from SEC EDGAR Form 8-K item codes (1.05 cyber incident, 5.02 executive change, 1.01/2.01 M\&A, 4.02 restatement, 1.03 bankruptcy...). Ticker mapping, industry/state filters, 'only new' monitoring, optional AI summary. Official EDGAR API, public domain.

- **URL**: https://apify.com/tendoyo/sec-8k-event-signals.md
- **Developed by:** [Shuai Li](https://apify.com/tendoyo) (community)
- **Categories:** Business, News, Lead generation
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 filing signals

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 8-K Event Signals – cyber incidents, executive changes, M\&A, restatements

Turn SEC EDGAR into a clean feed of **material corporate events** for U.S.-listed companies, taken from Form 8-K item codes:

| Signal | 8-K items |
|---|---|
| Cyber incident | 1.05 |
| Executive change | 5.02 |
| M\&A | 1.01, 2.01, 5.01 |
| Restatement | 4.02 |
| Auditor change | 4.01 |
| Bankruptcy | 1.03 |
| Delisting notice | 3.01 |
| Layoffs / restructuring | 2.05 |
| Impairment | 2.06 |
| Debt default / acceleration | 2.04 |
| Earnings | 2.02 |

You can also pass any raw item code, a full-text `query` (e.g. `"ransomware"`), `tickers`, business `states`, `sicPrefixes` and a date window.

### Why this Actor

- **Item matching is verified, not trusted.** EDGAR full-text search sometimes ignores its own `items` filter and returns unrelated or cached results. This Actor scans every 8-K in the window, groups documents by accession number (main document preferred over exhibits) and matches items client-side. You never get a "cyber incident" row that is really an earnings release.
- **Rare events are not crowded out.** Rare, high-severity groups (cyber, restatement, auditor change…) are filled first, and each requested signal gets a fair share of `maxItems`.
- **Ready to use rows.** Each row has ticker(s) from SEC's ticker map, CIK, SIC, state, severity, a direct link to the primary document and the filing index. With `includeDocumentText`, you also get a 4,000-character excerpt that starts at the first "Item x.xx".
- **Optional AI summary (bring your own key).** It returns headline, event type, key facts, effective date, financial impact, shareholder sentiment and a *sales trigger* (why a vendor might reach out now). People are referred to by role only.
- **`onlyNew`** for daily alert schedules.

### Pricing (pay per event)

- Filing signal: **$0.004**
- AI filing summary: **$0.01**

### Data source

SEC EDGAR full-text search and archives. This is a U.S. government work in the public domain. The Actor follows SEC fair-access rules: a declared User-Agent with a contact e-mail (set `contactEmail`) and about 4 requests/s, well under the 10/s limit.

*Not investment advice.*

### Try it in one click

These ready-made example tasks show real output. Open one, click **Try for free** and you get your own copy to edit and run:

- [Monitor 8-K cybersecurity incidents and CEO/CFO changes](https://apify.com/Tendoyo/sec-8k-event-signals/examples/sec-8k-cyber-exec-last-7-days)
- [Track 8-K M\&A, layoffs and bankruptcy filings](https://apify.com/Tendoyo/sec-8k-event-signals/examples/sec-8k-mna-distress-last-14-days)

### Sample output

Real rows from a recent run (some fields trimmed). The full row schema is shown in the **Output** tab.

```json
[
  {
    "companyName": "Getty Images Holdings, Inc.",
    "tickers": [
      "GETY",
      "GETYQ"
    ],
    "fileDate": "2026-10-26",
    "items": [
      "1.01",
      "1.03",
      "2.03",
      "9.01"
    ],
    "itemDescriptions": [
      "Entry into a Material Definitive Agreement",
      "Bankruptcy or Receivership",
      "Creation of a Direct Financial Obligation",
      "Financial Statements and Exhibits"
    ],
    "signals": [
      "bankruptcy",
      "mergersAcquisitions"
    ],
    "severity": "high",
    "businessLocation": "Seattle, WA",
    "documentUrl": "https://www.sec.gov/Archives/edgar/data/1898496/000121390026112265/ea0309581-8k_getty.htm",
    "documentTextExcerpt": "Item 1.01. Entry into a Material Definitive Agreement. As previously disclosed, on October 12, 2026, Getty Images Holdings, Inc. (the “Company”) and certain of…"
  },
  {
    "companyName": "Leslie's, Inc.",
    "tickers": [
      "LESL",
      "LESLQ"
    ],
    "fileDate": "2026-10-22",
    "items": [
      "1.03",
      "9.01"
    ],
    "itemDescriptions": [
      "Bankruptcy or Receivership",
      "Financial Statements and Exhibits"
    ],
    "signals": [
      "bankruptcy"
    ],
    "severity": "high",
    "businessLocation": "Phoenix, AZ",
    "documentUrl": "https://www.sec.gov/Archives/edgar/data/1821806/000119312526428048/lesl-20261020.htm",
    "documentTextExcerpt": "Item 1.03 Bankruptcy or Receivership. As previously reported, on September 30, 2026 (the “Petition Date”), Leslie’s, Inc. (the “Company”) and its subsidiaries L…"
  }
]
```

### How much does it cost?

You pay only for results (pay per event). There is no separate compute charge, and you can cap any run with **Max total charge**.

| Scenario | Cost |
|---|---|
| 25 filing signals (one example run) | 25 × $0.004 = **$0.10** |
| Daily cyber + exec-change alert, ~10 filings/day | 300 × $0.004 ≈ **$1.20 / month** |
| Same, with AI summaries (your own LLM key) | + 300 × $0.01 = **+$3.00 / month** |

A tiny "Actor start" event (about $0.00005) is also charged once per run.

### Use it from your code or tools

Run it and get the results in one call:

```bash
curl -X POST "https://api.apify.com/v2/acts/Tendoyo~sec-8k-event-signals/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"signals": ["cyberIncident"], "daysBack": 1, "maxItems": 50}'
```

```python
from apify_client import ApifyClient
client = ApifyClient("<APIFY_TOKEN>")
run = client.actor("Tendoyo/sec-8k-event-signals").call(run_input={"signals": ["cyberIncident"], "daysBack": 1, "maxItems": 50})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)
```

To get alerts, add a **Schedule** (for example daily at 07:00) with `onlyNew: true` where available. Then connect **Slack, e-mail, Google Sheets, Make, Zapier, n8n or a webhook** in the Integrations tab. It also works with AI agents through the Apify MCP server.

### FAQ

**Is this real-time?**
EDGAR publishes 8-Ks within minutes of acceptance. Schedule the Actor hourly or daily with `onlyNew: true` and you receive each filing once.

**Do I need an SEC API key?**
No. EDGAR is free public data. You only need an Apify account; optionally set `contactEmail` so SEC can identify your traffic.

**Why are some filings tagged with several signals?**
An 8-K can report several items at once, e.g. a merger agreement (1.01) plus a bankruptcy filing (1.03). `signals` lists all of them; `matchedItems` shows which ones matched your filter.

**Can I filter by ticker or industry?**
Yes: `tickers`, `sicPrefixes` (SIC industry codes) and business `states`, or a free-text `query` such as "ransomware".

**Is it investment advice?**
No. It is a data feed of public filings. Always read the source document (`documentUrl`).

### Support

Questions, bugs or a source you'd like added: open an issue on the Actor page or e-mail **youcanneverhacktendoyo@gmail.com**. Maintained by [Tendoyo](https://apify.com/Tendoyo).

# Actor input Schema

## `signals` (type: `array`):

Event groups mapped to 8-K item codes, e.g. cyber (1.05), executiveChange (5.02), mna (1.01/2.01/5.01), restatement (4.02).

## `items` (type: `array`):

e.g. 8.01, 7.01

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

Optional, e.g. ransomware or "artificial intelligence"

## `tickers` (type: `array`):

Empty = all companies.

## `states` (type: `array`):

e.g. CA, NY, TX

## `sicPrefixes` (type: `array`):

e.g. 73 (software/IT services), 28 (pharma), 60 (banks)

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

How many days back to look, counting from today (UTC).

## `filedSince` (type: `string`):

ISO date (YYYY-MM-DD). Overrides "Days back".

## `filedUntil` (type: `string`):

ISO date (YYYY-MM-DD). Defaults to today.

## `includeAmendments` (type: `boolean`):

Also include 8-K/A amendment filings.

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

Maximum number of filing signals to output (and charge for). Rare high-severity signals are filled first.

## `maxScanDocuments` (type: `integer`):

EDGAR indexes every document of a filing (8-K body + exhibits). Item matching is done client-side over all 8-K documents in the date window, so wider windows need more scanning (~1,500 documents per week of filings, 100 per request).

## `onlyNew` (type: `boolean`):

Skip items already delivered by previous runs of this Actor (state kept in a named key-value store). Ideal for daily schedules.

## `includeDocumentText` (type: `boolean`):

Add a ~4,000-character excerpt of the 8-K starting at the first "Item x.xx".

## `llmEnrichment` (type: `boolean`):

Optional AI summary per filing (headline, key facts, impact, sales trigger). Requires your own OpenAI-compatible key.

## `llmApiKey` (type: `string`):

Your API key for any OpenAI-compatible endpoint. Stored encrypted; only used when the AI option is on.

## `llmBaseUrl` (type: `string`):

Base URL of an OpenAI-compatible API, e.g. https://api.openai.com/v1.

## `llmModel` (type: `string`):

Model name passed to the OpenAI-compatible endpoint.

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

SEC asks automated clients to identify themselves.

## Actor input object example

```json
{
  "signals": [
    "cyberIncident",
    "executiveChange"
  ],
  "daysBack": 7,
  "includeAmendments": false,
  "maxItems": 100,
  "maxScanDocuments": 5000,
  "onlyNew": false,
  "includeDocumentText": false,
  "llmEnrichment": false
}
```

# Actor output Schema

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

One row per 8-K filing with mapped event signals, tickers, severity and links, plus optional AI summary.

## `runSummary` (type: `string`):

JSON stats for the run: items pushed, sources queried, charged events and warnings.

# 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 = {
    "signals": [
        "cyberIncident",
        "executiveChange"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("tendoyo/sec-8k-event-signals").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 = { "signals": [
        "cyberIncident",
        "executiveChange",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("tendoyo/sec-8k-event-signals").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 '{
  "signals": [
    "cyberIncident",
    "executiveChange"
  ]
}' |
apify call tendoyo/sec-8k-event-signals --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,tendoyo/sec-8k-event-signals"
        }
    }
}
```

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/ZlmmNxSoeD6rDo2Ly/builds/QojunMPNYoA4zPJDg/openapi.json