# SEC Form 144 Scraper: Insider Planned Sales (`parselab/sec-form-144-planned-sales-scraper`) Actor

Scrape SEC Form 144 notices of planned insider stock sales by ticker or across the market. Get the seller and role, shares, value, percent of shares outstanding, broker, how the shares were acquired, 10b5-1 plan dates and past sales. Spot cluster selling. Export to CSV or Excel.

- **URL**: https://apify.com/parselab/sec-form-144-planned-sales-scraper.md
- **Developed by:** [ParseLab](https://apify.com/parselab) (community)
- **Categories:** Business, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $18.00 / 1,000 results

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 Form 144 Scraper: Insider Planned Sales

This SEC Form 144 scraper reads the notices that officers, directors and large shareholders must file before they sell restricted or control shares. It is the early warning that comes days before the sale shows up as a Form 4. Follow a list of tickers, or leave the company empty and scan every notice filed in a date range. Each notice comes back as one clean row.

A row carries much more than the name of the seller. You get the company and ticker, the seller and the role, the number of shares and their market value, the implied price, the percent of all shares of the company, the broker that will execute the sale, how and when the shares were acquired (option exercise, restricted stock units, gift, purchase), the Rule 10b5-1 trading plan adoption date and how long the plan has been in place, the sales of the last three months with proceeds, and data warnings for notices with typing errors.

Investors, analysts, journalists, newsletter writers and quant researchers use it to see insider selling before it happens and to tell planned selling from selling that is not planned.

### What can you do with this Form 144 scraper?

- See every planned insider sale of a stock in the last six months
- Find the biggest planned sales across the market this week
- Separate sales under a 10b5-1 trading plan from sales without a plan
- See how many shares an executive plans to sell compared with all shares of the company
- Find cluster selling, when three or more insiders of one company file in the same period
- Check how an executive got the shares: option exercise, restricted stock units, gift or purchase
- See which broker will handle the sale
- Read the sales of the last three months next to the new plan
- Follow a single insider across companies
- Export Form 144 data to CSV or Excel, or send new notices to Slack or your own tools

### What data can you extract from Form 144 filings?

| Mode | One row is | Highlights |
|---|---|---|
| Notices | One Form 144 | Company, ticker, exchange, location, seller, relationships and flags for officer, director and 10 percent owner, form and amendment flag, filing, notice and sale dates, days from filing to sale, share class, shares, market value, implied price, shares outstanding and percent of the company, broker name and city, acquisition details with nature, date, source and amount, option exercise and gift flags, days held, trading plan date and flag, days from plan adoption to sale, sales of the last three months with proceeds, signer, data warnings, filing links |
| Companies | One company | Notices, unique sellers and their names, total shares and value, share of the company, officer, director, trading plan and option exercise notices, cluster selling flag, biggest sale, first and last notice dates |
| Sellers | One insider | Roles, notices, companies, total shares and value, trading plan notices, brokers, first and last notice dates |

### How to scrape SEC Form 144 filings

1. Choose **Notices**, **Companies** or **Sellers**.
2. Enter tickers, or leave them empty to scan the whole market.
3. Set the filing dates. The default is the last 3 days, or 180 days when you choose a company.
4. Optionally add a minimum value, a role, a seller name or the trading plan filter.
5. Turn on **Hide suspect notices** to drop typing errors.
6. Set **Max Items** and click **Start**.
7. Export the dataset as CSV, Excel or from the Apify console.

### Input example

```json
{
  "mode": "filings",
  "relationships": ["Officer", "Director"],
  "minValueUsd": 1000000,
  "excludeSuspect": true,
  "dateFrom": "2026-09-28",
  "dateTo": "2026-10-02",
  "maxItems": 100
}
```

### Notice output example

```json
{
  "issuerName": "Workday, Inc.",
  "ticker": "WDAY",
  "exchange": "NASDAQ",
  "sellerName": "Gerrit Kazmaier",
  "relationships": ["Officer"],
  "filingDate": "2026-10-06",
  "approxSaleDate": "2026-10-06",
  "sharesToSell": 2729,
  "aggregateMarketValueUsd": 515671.84,
  "impliedPricePerShare": 188.96,
  "sharesOutstanding": 196000000,
  "percentOfOutstanding": 0.0014,
  "brokerName": "Morgan Stanley Smith Barney LLC Executive Financial Services",
  "acquisitionNature": ["Restricted Stock Units"],
  "tradingPlanAdoptedOn": "2025-09-19",
  "isTradingPlanSale": true,
  "daysFromPlanAdoptionToSale": 382,
  "soldInPast3Months": true,
  "pastSharesSold": 2728,
  "pastGrossProceedsUsd": 391785.54,
  "hasDataWarnings": false
}
```

### Company view example

```json
{
  "issuerName": "Elastic N.V.",
  "ticker": "ESTC",
  "notices": 3,
  "uniqueSellers": 3,
  "totalMarketValueUsd": 146826267,
  "clusterSelling": true,
  "tradingPlanNotices": 0
}
```

### How much does it cost to scrape Form 144 filings?

You pay per result: $24 per 1,000 rows plus a tiny start fee. The free plan returns up to 10 rows per run. The company and seller views return one row per group, so a week of the whole market costs a few cents.

### Tips for better results

- A Form 144 says an insider plans to sell. The sale may happen on the date given, later, or not at all. The Form 4 that follows confirms what was sold.
- Sales under a Rule 10b5-1 plan were decided when the plan was adopted. The plan date and the days from plan to sale tell you how old the decision is.
- Compare the shares to sell with the shares outstanding. Millions of shares sold by an executive can still be a tiny share of a large company.
- Anyone can file a Form 144, so a few notices contain typing errors, such as a wrong number of shares. The data warnings flag them and one switch hides them.
- Cluster selling means three or more different sellers in one company in the period. It says more than one large sale.
- A normal business day has around 130 notices. Use the date range wisely for long periods and raise the limit of filings to scan.
- For a daily alert, schedule the Actor every morning and turn on the option to return only notices not returned before.

### Who uses Form 144 data?

- **Investors** watch what insiders plan before the market sees it.
- **Analysts** study selling by role, plan and size.
- **Journalists** report on large executive sales.
- **Newsletter writers** publish weekly insider selling lists.
- **Quant researchers** build signals from planned sales.

### Automate and connect

Schedule the Actor every day and send new notices to Slack, Google Sheets, Zapier, Make or n8n, or trigger a webhook when a run ends.

### FAQ

**Do I need an SEC account?**
No. The Actor works without any login.

**What is a Form 144?**
A notice that an insider files with the SEC when they plan to sell restricted shares or shares that they hold as an affiliate of the company, above small limits.

**Is a Form 144 the same as a Form 4?**
No. The Form 144 is filed before the sale and states a plan. The Form 4 is filed after the trade and states what happened. See the SEC Insider Trading Scraper for Form 4.

**Why do some notices show a trading plan and others do not?**
Only notices where the insider states a Rule 10b5-1 plan adoption date are flagged as trading plan sales.

**Why are some values odd?**
The form is filled in by the filer. The Actor reports what was filed and adds warnings when the numbers look wrong.

**How far back can I search?**
Use the filing dates to choose the period. Form 144 has been filed electronically in structured form since 2023.

**Is this financial advice?**
No. Form 144 notices are public information. Use them as one input among many.

### Legal note

This Actor collects information that is publicly visible on the website. Check the source site's terms and your local rules before using the data. Nothing here is financial advice.

### Support

Missing a field or found a bug? Open an issue from the Actor page.

# Actor input Schema

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

Free users: Limited to 10 items (preview). Paid users: Optional, max 1,000,000.

## `mode` (type: `string`):

Notices returns one row per Form 144 with the planned sale. Companies returns one row per company with the total planned selling and cluster selling. Sellers returns one row per insider with the notices of the period.

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

Tickers of the companies to follow, for example NVDA, AAPL. With a company the default start date is 180 days ago. Leave empty to scan all companies in the date range.

## `ciks` (type: `array`):

SEC company numbers of the issuers, for companies without a ticker.

## `companyNames` (type: `array`):

Part of a name, for example Therapeutics or Smith. Only notices where the company or the filer has a name containing the text are read.

## `sellerNames` (type: `array`):

Part of the name of the insider who plans to sell, for example Cook or Zuckerberg.

## `relationships` (type: `array`):

Keep only sellers with this relationship, for example Officer, Director or 10 percent owner. Any match keeps the notice.

## `exchanges` (type: `array`):

Part of the exchange name, for example NASDAQ or NYSE.

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

Keep only notices where the shares to sell are worth at least this much, for example 1000000.

## `minShares` (type: `integer`):

Keep only notices for at least this many shares.

## `minPercentOfOutstanding` (type: `number`):

Keep only notices that cover at least this percent of all shares of the company, for example 0.5.

## `onlyTradingPlans` (type: `boolean`):

Keep only notices that mention a Rule 10b5-1 plan adoption date. These sales were set up in advance and say less about the current view of the insider.

## `excludeSuspect` (type: `boolean`):

Hide notices with data warnings, such as more shares than the company has, an implied price under one cent or an unusual relationship. Anyone can file a Form 144, so a few notices contain typing errors.

## `excludeAmendments` (type: `boolean`):

Skip Form 144/A amendments.

## `dateFrom` (type: `string`):

First filing date, YYYY-MM-DD. The default is 3 days ago, or 180 days ago when you choose companies.

## `dateTo` (type: `string`):

Last filing date, YYYY-MM-DD. The default is today.

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

Skips notices that an earlier run already returned. Use it for daily alerts.

## `maxFilingsToScan` (type: `integer`):

Safety limit for how many notices are read before the run stops, even when few match your filters.

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

Added to the request header as SEC fair access guidelines recommend. Leave empty if you prefer.

## Actor input object example

```json
{
  "maxItems": 10,
  "mode": "filings",
  "onlyTradingPlans": false,
  "excludeSuspect": false,
  "excludeAmendments": false,
  "onlyNewSinceLastRun": false,
  "maxFilingsToScan": 3000
}
```

# Actor output Schema

## `overview` (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 = {
    "maxItems": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("parselab/sec-form-144-planned-sales-scraper").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 = { "maxItems": 10 }

# Run the Actor and wait for it to finish
run = client.actor("parselab/sec-form-144-planned-sales-scraper").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 '{
  "maxItems": 10
}' |
apify call parselab/sec-form-144-planned-sales-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,parselab/sec-form-144-planned-sales-scraper"
        }
    }
}
```

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/5pVETvq6Mh4bjwJmx/builds/MpmhWTHKhHVZeXBjc/openapi.json