# SEC Insider Trading Alerts: Form 4 Buys & Sells (`accountable_eel/sec-insider-trading-alerts`) Actor

Get every insider buy or sell (SEC Form 4) for a list of tickers or the whole market, filtered by role (CEO and CFO insider buys), type and size (purchases over $100k), with cluster detection. Alerts to Slack, Discord or Telegram when filed. Export insider transactions to Google Sheets or n8n.

- **URL**: https://apify.com/accountable_eel/sec-insider-trading-alerts.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 $2.50 / 1,000 insider transaction returneds

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 Insider Trading Alerts: Form 4 Buys & Sells

**Every insider buy or sell (SEC Form 4) for your tickers or across the whole market, as it is filed.** Each non-derivative transaction an officer, director or 10% owner reports to the SEC: the insider, their role and title, the shares, the price, the dollar value, the shares they hold afterwards, and a link to the real filing. Filter by transaction type, role and dollar size. Turn on monitoring and each new transaction goes to your Slack, Discord or Telegram the day it is filed. Turn on cluster mode and you only get companies where several different insiders bought within the same window.

This reports public SEC filings. It is not investment advice and contains no trading signals.

### How to use

1. **In the Apify Console.** Open the actor page and click **Start** — the `tickers` 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-insider-trading-alerts/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"tickers":[""]}'
   ```
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
{
  "tickers": [
    ""
  ]
}
```

Optional. One stock ticker per line (e.g. AAPL, NVDA). Leave empty to get insider transactions from the whole market in the date window below. Each ticker is matched to its SEC filer and only Form 4 filings for that company are searched. Accepted formats: AAPL, NVDA, TSLA.

```json
{
  "sinceDays": 7,
  "industryKeywords": ["Biotechnology"],
  "states": ["CA", "NY"],
  "minAmountUsd": 1000000,
  "onlyNewSinceLastRun": true
}
```

This actor is one search over a date window, not a per-line lookup: `sinceDays` sets how far back to
search (default 7, up to 90), `industryKeywords`/`states`/`minAmountUsd` are optional filters applied
before you're billed, and `maxResults` (default 100, up to 1,000) is what actually caps the run's cost
— SEC files hundreds of Form D filings a day across all industries. Turn on `onlyNewSinceLastRun` to
get only filings this watchlist hasn't returned before, charged nothing on a quiet day.

### Output

One row per item, for example:

| query | found | status | transactionCount | issuerName | issuerCik | ticker | insiderName | insiderCik | role | officerTitle | transactionDate | filedAt | transactionCode | transactionType | shares | pricePerShare | valueUsd | sharesOwnedAfter | directOrIndirect | accessionNumber | filingUrl | isAmendment | isNew | firstSeenAt | scrapedAt |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
|  | true | OK | <transactions returned> | \<company (issuer)> | <issuer sec cik> | <ticker> | \<insider (reporting owner)> | <insider sec cik> | <role> | <officer title> | <transaction date> | <filed on> | <transaction code> | <transaction type> | <shares> | \<price per share (usd)> | \<value (usd)> | <shares owned after this transaction> | \<direct (d) or indirect (i) ownership> | <accession number> | <sec filing page> | \<is this an amended form 4 (4/a)?> | \<is this new since the last run?> | <first seen by this watchlist> | 1970-01-01T00:00:00.000Z |

A miss comes back as a row with `"found": false` and is never charged.

### Pricing

- **Insider transaction returned**: $5 per 1,000 transactions

Plus a $0.002 start fee per run. Each event above is billed independently, only when it actually returns data — misses (`found:false`) are never charged.

### 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-insider-trading-alerts/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"tickers":[""]}'
```

**n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~sec-insider-trading-alerts/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body Content Type `JSON`, JSON Body `{"tickers":[""]}` (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-insider-trading-alerts/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body `{"tickers":["{{transaction}}"]}`, mapping the row's transaction into the `tickers` array.

**MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "SEC Form 4 insider trading alerts" — the agent will find and run this actor.

### What this is not

- Not investment advice. The actor reports SEC filings and applies the filters you set. It has no ratings, no scores and no recommendations.
- Not a real-time feed. An insider has two business days after a trade to file, so a transaction shows up here on the day it is filed, not the day it happened.
- Not every insider transaction. Only non-derivative transactions (shares, not options) are returned. A filing with options only has nothing to return and is not billed.

### Monitoring and alerts

Turn on **Only return transactions that are new since the last run** to make this an alert. Each transaction is recorded in a named store for 90 days after its filing date, so a repeat run returns only what is new. A quiet run costs only the start fee.

Paste a **Discord or Slack webhook**, a **Telegram bot link**, or any URL into **Send alerts to** and each new transaction is posted there as one message. Only transactions that are billed are posted. A failed message never fails the run; the row's `notifyErrors` says why, without the link.

### Cluster mode

Set **Cluster: minimum number of different insiders buying** to 2 or more. The actor counts distinct insiders who made open-market buys in one company within the cluster window (default 14 days). The count uses this run's buys plus the buys the watchlist already saw, so it works across scheduled runs. Only transactions from qualifying companies are returned. Cluster mode needs buys (`P`) in the transaction code.

### Related actors

- [SEC EDGAR API: Company Lookup by Ticker or CIK, Latest Filings](https://apify.com/accountable_eel/sec-edgar-company-lookup): company details and latest filings by ticker or CIK.

### Example runs

**Open-market buys across the market, last 2 days (the default daily test)**

```json
{ "sinceDays": 2, "transactionCodes": "P", "maxResults": 10 }
```

**C-suite open-market buys of $100k or more, for two tickers, last 7 days**

```json
{ "tickers": ["AAPL", "NVDA"], "sinceDays": 7, "transactionCodes": "P", "roles": "cSuite", "minValueUsd": 100000 }
```

**Cluster: 3 or more different insiders bought the same company within 14 days (schedule this one)**

```json
{ "transactionCodes": "P", "clusterMinInsiders": 3, "clusterDays": 14, "sinceDays": 14, "onlyNewSinceLastRun": true, "deltaName": "cluster-buys" }
```

# Actor input Schema

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

Optional. One stock ticker per line (e.g. AAPL, NVDA). Leave empty to get insider transactions from the whole market in the date window below. Each ticker is matched to its SEC filer and only Form 4 filings for that company are searched. Accepted formats: AAPL, NVDA, TSLA. You're only charged for the ones we actually find — a miss costs nothing.

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

How far back to search for Form 4 filings, in days (up to 30). A Form 4 is due within two business days of the trade, so 2 covers the most recent filing day. The date window is a search bound; "Stop after this many transactions" is what caps how many you get and pay for.

## `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 1,000. The real cost control: each returned transaction is billed. A run stops fetching filings once this many transactions match.

## `transactionCodes` (type: `string`):

P is an open-market purchase with the insider's own money, the signal most people want. S is an open-market sale. "all" also returns grants, option exercises, tax withholding and gifts, which are routine and not a market signal.

## `roles` (type: `string`):

Filters by the role the insider reported on the filing. C-suite matches the officer title: CEO, CFO, COO, President, or any "Chief …" title.

## `minValueUsd` (type: `integer`):

Optional. Only keep transactions worth at least this much (shares × price). A transaction with no reported price can't be shown to meet a minimum, so it is dropped whenever this is set.

## `clusterMinInsiders` (type: `integer`):

0 (off) returns every matching transaction. Set to 3, for example, to return only companies where at least 3 DIFFERENT insiders made open-market buys within the cluster window below. The count is this run's buys plus the buys the monitoring watchlist already saw. Cluster mode needs the transaction code to include P.

## `clusterDays` (type: `integer`):

Only used with the cluster minimum above. Up to 90.

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

Turns this into an alert: a transaction counts as new when this watchlist has not returned it before. Transactions already seen are dropped before you are billed, so a quiet run returns one summary row and costs only the start fee. A transaction is forgotten 90 days after its filing date.

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

Leave empty to use the one shared watchlist for this account — changing your tickers or filters between runs still narrows the SAME watchlist. Type a name to keep two separate schedules (e.g. one for buys, one for sales) from marking each other's transactions as seen.

## `notifyUrl` (type: `string`):

Optional. After the transactions are billed, each NEW transaction is posted here as one message: who, what, how many shares, price, value, the filing date and a link to the SEC filing. Discord or Slack: paste the channel's webhook URL. Telegram: https://api.telegram.org/bot<token>/sendMessage?chat_id=<chat id>. Any other URL receives JSON. Messages are free, and a message that fails never fails the run (the row's notifyErrors says why). Stored encrypted, never logged or written to the results.

## `notifyFormat` (type: `string`):

Leave on "Detect from the link": discord.com links get Discord messages, hooks.slack.com Slack, api.telegram.org Telegram, anything else JSON. Pick one only to override that.

## `maxNotificationsPerRun` (type: `integer`):

Up to 100. Above this, one "+N more" message says how many more transactions are in the run's dataset, so a busy run never floods the channel. 0 sends only that one summary message.

## `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 transaction found gets its own row instead of being grouped under its transaction. You're still only charged once per transaction, 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.

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

Apify Proxy config. Residential recommended for anti-bot-sensitive targets.

## Actor input object example

```json
{
  "tickers": [
    ""
  ],
  "sinceDays": 2,
  "testRun": false,
  "onlyFound": false,
  "includeKeywords": [],
  "excludeKeywords": [],
  "maxResults": 100,
  "transactionCodes": "P",
  "roles": "any",
  "minValueUsd": 0,
  "clusterMinInsiders": 0,
  "clusterDays": 14,
  "onlyNewSinceLastRun": false,
  "deltaName": "",
  "notifyFormat": "auto",
  "maxNotificationsPerRun": 20,
  "columns": [
    "transactionCount",
    "issuerName",
    "issuerCik",
    "ticker",
    "insiderName",
    "insiderCik",
    "role",
    "officerTitle",
    "transactionDate",
    "filedAt",
    "transactionCode",
    "transactionType",
    "shares",
    "pricePerShare",
    "valueUsd",
    "sharesOwnedAfter",
    "directOrIndirect",
    "accessionNumber",
    "filingUrl",
    "isAmendment",
    "isNew",
    "firstSeenAt"
  ],
  "expandRows": true,
  "maxConcurrency": 5,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# 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 = {
    "tickers": [
        ""
    ],
    "includeKeywords": [],
    "excludeKeywords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/sec-insider-trading-alerts").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 = {
    "tickers": [""],
    "includeKeywords": [],
    "excludeKeywords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/sec-insider-trading-alerts").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 '{
  "tickers": [
    ""
  ],
  "includeKeywords": [],
  "excludeKeywords": []
}' |
apify call accountable_eel/sec-insider-trading-alerts --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,accountable_eel/sec-insider-trading-alerts"
        }
    }
}
```

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/qxMvPoMMQ9okdyDJX/builds/wGmmU3zwXLR3vfUQK/openapi.json
