# 8-K Filings Scraper: Company Buying Signals (`agents001/form-8k-company-events`) Actor

Returns recent Form 8-K filings as company buying signals: new agreements, acquisitions, officer or director changes, bankruptcies, results and more, with plain-English event labels, ticker, CIK, industry, state and filing link. Daily mode returns only new filings.

- **URL**: https://apify.com/agents001/form-8k-company-events.md
- **Developed by:** [Mike Ross](https://apify.com/agents001) (community)
- **Categories:** Lead generation, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.40 / 1,000 8-k filing events

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

## 8-K Filings Scraper: Company Buying Signals

Get a clean daily list of US public companies that just reported a major event: **one record per Form 8-K filing**, with the company name, CIK, ticker, industry, state of incorporation, business location, the event item codes with plain-English labels, the filing date and a link to the filing.

Form 8-K is the "current report" public companies must file within four business days of a major event. That makes it one of the fastest public trigger feeds for sales and business development teams:

- **1.01 Signed a major agreement**: new customers, suppliers, partnerships and credit deals.
- **2.01 Completed an acquisition or sale of assets**: new owners, new systems, integration projects.
- **5.02 Officer or director change**: a new executive often reviews vendors in the first 90 days. The Actor reports only that a change happened. It never returns the names of the people involved.
- **1.03 Bankruptcy**, **2.05 Restructuring**, **3.01 Delisting notice**: distress signals for turnaround, advisory and credit teams.
- **2.02 Results**, **7.01 Investor communication**, **8.01 Other events** and every other 8-K item.

### What you get

| Field | Example |
|---|---|
| `companyName`, `cik`, `ticker`, `tickers` | `XCF Global, Inc.`, `0002019793`, `SAFX`, `["SAFX"]` |
| `primaryEvent`, `primaryEventCode` | `Completed an acquisition or sale of assets`, `2.01` (the most sales-relevant event in the filing) |
| `eventItemCodes`, `eventLabels`, `eventSummary` | `["1.01", "2.01", "5.02"]`, plain-English labels, one readable line |
| `eventCategories` | `agreement`, `acquisition`, `leadership-change`, `distress`, `financing`, `restructuring` and more |
| `events` | Each item with code, plain label, official 8-K title and category |
| `hasDealOrAcquisition`, `hasLeadershipChange`, `hasDistressSignal` | Yes or no flags for quick filtering in a spreadsheet or CRM |
| `industry`, `sicCode`, `sicDescription` | `Industrial Organic Chemicals`, `2860`, `INDUSTRIAL ORGANIC CHEMICALS` |
| `stateOfIncorporation`, `stateOfIncorporationName` | `DE`, `Delaware` |
| `businessState`, `businessLocation` | `TX`, `Houston, TX` (company business address city and state) |
| `formType`, `isAmendment` | `8-K`, `false` |
| `filedDate`, `periodOfReport` | `2026-10-22`, `2026-10-16` (date of the event) |
| `accessionNumber`, `filingUrl`, `documentUrl`, `companyFilingsUrl` | Filing id, filing index page, main document, the company's 8-K history |
| `coRegistrants` | Other companies named on the same filing (company name and CIK) |

The Output tab has two views: **Company events** and **Sales signals**.

### Quick start

1. Click **Start**. With the example input you get filings from the last 3 days that report a major agreement, a completed acquisition or an officer or director change.
2. Narrow it down: pick the **event types** you care about, add **SIC codes** for your target industries (for example `7372` software or `28` chemicals and pharma), and **states** for your territory.
3. Watching named accounts? Add their **tickers or CIK numbers** under Companies.
4. Schedule it daily with **Only filings not seen in previous runs** switched on and send the results to email, Slack, Google Sheets or your CRM with an Apify integration or webhook.

A default run (no input) finishes in a few seconds and returns up to 200 filings.

### Input

| Field | What it does | Default |
|---|---|---|
| `daysBack` | Filings from today back this many days (US Eastern time) | 3 |
| `startDate`, `endDate` | A fixed window, `YYYY-MM-DD` | none |
| `itemCodes` | Only filings with at least one of these items | all items |
| `excludeItemCodes` | Skip filings whose only events are these items (9.01 exhibits are ignored) | none |
| `sicCodes` | SIC code or prefix, for example `7372` or `73` | all industries |
| `states` | Business address state, for example `CA`, `NY` | all |
| `incorporationStates` | State or country of incorporation, for example `DE`, `NV`, `E9` (Cayman Islands) | all |
| `companies` | Tickers (`AAPL`, `BRK.B`) or CIK numbers (`320193`) | all companies |
| `includeAmendments` | Also return 8-K/A amendments | false |
| `maxItems` | Stop after this many filings. `0` means no limit | 200 |
| `onlyNew` | Only filings not returned before for the same filters | false |
| `userAgent` | Identification sent to SEC. You can put your company name and contact email here | the Actor's own |

Example input for a daily sales-trigger feed for software companies in California and New York:

```json
{
  "daysBack": 1,
  "itemCodes": ["1.01", "2.01", "5.02"],
  "sicCodes": ["7370", "7371", "7372", "7373", "7374"],
  "states": ["CA", "NY"],
  "onlyNew": true,
  "maxItems": 500
}
```

### Output example

```json
{
  "companyName": "Leslie's, Inc.",
  "cik": "0001821806",
  "ticker": "LESL",
  "tickers": ["LESL", "LESLQ"],
  "primaryEvent": "Bankruptcy or receivership",
  "primaryEventCode": "1.03",
  "eventSummary": "1.03 Bankruptcy or receivership; 9.01 Financial statements and exhibits",
  "eventItemCodes": ["1.03", "9.01"],
  "eventCategories": ["distress", "exhibits"],
  "hasLeadershipChange": false,
  "hasDealOrAcquisition": false,
  "hasDistressSignal": true,
  "industry": "Retail: Retail Stores, NEC",
  "sicCode": "5990",
  "stateOfIncorporation": "DE",
  "stateOfIncorporationName": "Delaware",
  "businessState": "AZ",
  "businessLocation": "Phoenix, AZ",
  "formType": "8-K",
  "filedDate": "2026-10-22",
  "accessionNumber": "0001193125-26-428048",
  "filingUrl": "https://www.sec.gov/Archives/edgar/data/1821806/000119312526428048/0001193125-26-428048-index.htm"
}
```

A run report is saved in the key-value store as `RUN_SUMMARY`: records returned, filings scanned, filtered out, already delivered, and any ticker that could not be found.

### Pricing

This Actor uses **pay per event** pricing, with platform usage included:

- **$2.00 per 1,000 filings** (`filing-event` event, $0.002 each) on the Free plan, lower on paid Apify plans: $1.80 (Bronze), $1.60 (Silver), $1.40 per 1,000 (Gold and above).

You only pay for filings saved to your dataset, so filters, `onlyNew` and `maxItems` keep costs down. All US companies together file roughly 250 to 350 Form 8-Ks on a normal business day, so a daily unfiltered feed costs well under $1 a day. Set a maximum cost per run in the run options and the Actor stops cleanly when it is reached.

### How "only new filings" works

When `onlyNew` is on, the Actor remembers the accession numbers it has already returned for your filters in a key-value store in your account called `agents001-sec-8k-company-events-state`. The next run skips those, so you are never charged twice for the same filing. The date window and `maxItems` are not part of the memory, so a daily schedule with `daysBack: 1` or `3` keeps one history. Changing any filter starts a fresh history. The last 50,000 accession numbers are kept.

With `onlyNew` off, the Actor does not open or update this store. If a run stops with a message that it cannot open the store (for example because another Actor in your account already uses that name), enter a different name in **State store name** and run again.

### Data source and privacy

All data comes from the official EDGAR full-text search service run by the US Securities and Exchange Commission. Filings on EDGAR are public information. The SEC states that information on its site may be copied or further distributed without permission, and asks users to cite the SEC as the source: **Source: U.S. Securities and Exchange Commission, EDGAR.**

The Actor follows the SEC fair access rules: it identifies itself with a User-Agent, sends at most 5 requests per second by default (SEC allows 10), and slows down when asked. A default run needs about 3 requests.

The Actor returns **company-level data only**. It reads filing metadata (company, items, dates, codes) and never opens the filing documents, so it does not return the names, emails or phone numbers of officers, directors or anyone else.

### FAQ

**How fresh is the data?**
Filings appear in EDGAR full-text search within minutes of being accepted. Each run reads it live.

**Why is the ticker empty for some companies?**
Only companies with listed securities have a ticker in EDGAR. Funds, debt issuers and many small companies have none. Every record has a CIK, which identifies the company exactly.

**Why does a filing list item 9.01?**
Item 9.01 means financial statements or exhibits (often a press release) are attached. It comes with most filings, so the Actor never picks it as the main event when another item is present.

**Can I get the name of the new executive?**
No. The Actor is built for company-level signals and does not return personal data. Open `filingUrl` to read the filing itself.

**Something looks wrong. What should I do?**
Open an issue on the Actor's Issues tab with the run link.

### Disclaimer

This Actor is independent and is not affiliated with, endorsed by or sponsored by the U.S. Securities and Exchange Commission. SEC and EDGAR are trademarks of the SEC and are used here only to describe the data source. Company names belong to their owners. This is not investment advice; check the original filing before acting on it.

# Actor input Schema

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

Return filings from today back this many calendar days (US Eastern time). The default of 3 means a Monday run still covers Friday. Ignored when Start date is set.

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

First filing date to include, YYYY-MM-DD. Overrides Days back.

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

Last filing date to include, YYYY-MM-DD. Defaults to today.

## `itemCodes` (type: `array`):

Only filings that report at least one of these items. Leave empty for all. Good sales triggers: 1.01 major agreement, 2.01 acquisition completed, 5.02 officer or director change, 1.03 bankruptcy, 2.05 restructuring.

## `excludeItemCodes` (type: `array`):

Skip filings whose only events are these items, for example 2.02 results or 7.01 investor communication. Item 9.01 (exhibits) is ignored here because it comes with most filings. A filing that also reports another item is kept.

## `sicCodes` (type: `array`):

Only companies whose SIC code starts with any of these, for example 7372 (prepackaged software), 73 (business services) or 28 (chemicals and pharma). Leave empty for all industries.

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

Only companies whose business address is in these US states (two-letter codes such as CA, NY, TX) or EDGAR country codes.

## `incorporationStates` (type: `array`):

Only companies incorporated in these states or countries, for example DE for Delaware or E9 for the Cayman Islands.

## `companies` (type: `array`):

Only these companies. Use stock tickers (AAPL, BRK.B) or CIK numbers (320193). Leave empty for all companies.

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

Also return amendments to earlier 8-K filings. Off by default because an amendment usually repeats an event already reported.

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

Stop after this many filings are saved. 0 means no limit. You pay per filing saved.

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

Remember which filings were already returned for these filters and only return new ones. Ideal for a daily schedule. The date window and Maximum records are not part of the memory, so a rolling window keeps the same history. Changing the filters starts a fresh history.

## `stateStoreName` (type: `string`):

Name of the key-value store in your account that remembers filings already returned (only used with onlyNew). Each different set of filters gets its own record inside it. If a run reports that it cannot open the store, enter a different name here.

## `userAgent` (type: `string`):

SEC asks automated tools to identify themselves, ideally with a company name and contact email, for example "Acme Sales Ops ops@acme.com". Leave empty to use the Actor's own identification.

## `maxRequestsPerSecond` (type: `number`):

Requests to SEC per second. SEC allows at most 10 per user; this Actor never goes above 8.

## Actor input object example

```json
{
  "daysBack": 3,
  "itemCodes": [
    "1.01",
    "2.01",
    "5.02"
  ],
  "includeAmendments": false,
  "maxItems": 200,
  "onlyNew": false,
  "stateStoreName": "agents001-sec-8k-company-events-state",
  "maxRequestsPerSecond": 5
}
```

# Actor output Schema

## `events` (type: `string`):

No description

## `salesSignals` (type: `string`):

No description

## `runSummary` (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 = {
    "itemCodes": [
        "1.01",
        "2.01",
        "5.02"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("agents001/form-8k-company-events").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 = { "itemCodes": [
        "1.01",
        "2.01",
        "5.02",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("agents001/form-8k-company-events").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 '{
  "itemCodes": [
    "1.01",
    "2.01",
    "5.02"
  ]
}' |
apify call agents001/form-8k-company-events --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,agents001/form-8k-company-events"
        }
    }
}
```

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/AwZIEwyau8SnahtLM/builds/HHIkbs7Bi0FDveFlE/openapi.json