# SEC Form 144 Insider Sales Scraper API (`pink_comic/sec-form-144-insider-sales`) Actor

Search official SEC EDGAR Form 144 proposed insider-sale notices by issuer, CIK, filer, security, broker, exchange, date, shares, value, acquisition, and amendment status.

- **URL**: https://apify.com/pink\_comic/sec-form-144-insider-sales.md
- **Developed by:** [Ava Torres](https://apify.com/pink_comic) (community)
- **Categories:** Business, Lead generation, AI
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 sec form 144 insider sales scraper api evidence items

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/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## SEC Form 144 Proposed Insider Sales Scraper API

Search official SEC EDGAR Form 144 notices by issuer/company/ticker, exact CIK or accession, filer, security, broker, filing date, proposed shares/value, acquisition nature, exchange, and amendment status. The actor uses SEC EFTS metadata and bounded official primary XML detail requests with an identifying SEC-compliant User-Agent.

### Fast start

```json
{"query":"NVIDIA","maxResults":1,"maxFilingsScanned":10}
```

The deterministic default returns the latest matching NVIDIA Form 144 notice. At pay-per-event pricing it costs at most **$0.0001 per start + $0.002 per dataset item = $0.0021**. `maxResults` is a total output cap; a buyer run charge limit reduces it before source work.

More examples:

```json
{"cik":"1045810","broker":"Charles Schwab","minProposedShares":50000,"maxResults":10}
```

```json
{"accessionNumber":"0001921094-25-001247","maxResults":1}
```

### Output and outcomes

Found rows include filing date/form/accession, issuer name and CIK, filer name and CIK, issuer relationships, proposed security class/shares/aggregate market value/date/exchange, broker, acquisition date/nature/source/payment, official filing document/index/search URLs, retrieval time, detail status, bounded-scan disclosure, and mandatory evidence limits.

`NO_MATCH` is explicit and does not prove absence. `SOURCE_UNAVAILABLE` means SEC remained unavailable after bounded retries. If one filing XML cannot be parsed or fetched, the actor retains source-linked EFTS metadata with `detailStatus=METADATA_ONLY_*`; detail-dependent filters will not falsely match missing values.

### Coverage and interpretation limits

Form 144 is a **filer-submitted notice of a proposed sale** of restricted or control securities. It is **not proof that a sale occurred**, an executed insider transaction, current ownership, identity verification, intent beyond the filing, market impact, SEC verification/approval, or investment advice. Proposed shares and values can differ from actual executions; notices can be amended. Blank fields mean only not present in the parsed filing. Results are bounded by `maxFilingsScanned`, and SEC indexing or filings can lag or change.

Confirm material decisions against the linked filing, later amendments, executed-trade disclosures where applicable, and other current sources.

### Official sources

- [SEC EDGAR search](https://www.sec.gov/edgar/search/)
- [SEC Form 144](https://www.sec.gov/about/forms/form144.pdf)

# Actor input Schema

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

SEC full-text query. Empty input safely defaults to NVIDIA.

## `cik` (type: `string`):

Optional exact issuer cik filter or result-control setting. See the README for source semantics and examples.

## `accessionNumber` (type: `string`):

Optional exact accession filter or result-control setting. See the README for source semantics and examples.

## `filer` (type: `string`):

Optional filer / selling person filter or result-control setting. See the README for source semantics and examples.

## `security` (type: `string`):

Optional security class filter or result-control setting. See the README for source semantics and examples.

## `broker` (type: `string`):

Optional broker or market maker filter or result-control setting. See the README for source semantics and examples.

## `exchange` (type: `string`):

Optional exchange filter or result-control setting. See the README for source semantics and examples.

## `acquisitionNature` (type: `string`):

Optional acquisition nature filter or result-control setting. See the README for source semantics and examples.

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

Optional filed from filter or result-control setting. See the README for source semantics and examples.

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

Optional filed through filter or result-control setting. See the README for source semantics and examples.

## `amendmentFilter` (type: `string`):

Optional amendments filter or result-control setting. See the README for source semantics and examples.

## `minProposedShares` (type: `integer`):

Optional minimum proposed shares filter or result-control setting. See the README for source semantics and examples.

## `minProposedAmount` (type: `number`):

Optional minimum proposed aggregate value (usd) filter or result-control setting. See the README for source semantics and examples.

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

Total paid dataset-item cap. Default costs at most $0.0021 including start.

## `maxFilingsScanned` (type: `integer`):

Bounds official filing-document requests used for detail filters.

## Actor input object example

```json
{
  "query": "NVIDIA",
  "amendmentFilter": "any",
  "minProposedShares": 0,
  "minProposedAmount": 0,
  "maxResults": 1,
  "maxFilingsScanned": 10
}
```

# 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 = {
    "query": "NVIDIA",
    "maxResults": 1,
    "maxFilingsScanned": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("pink_comic/sec-form-144-insider-sales").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 = {
    "query": "NVIDIA",
    "maxResults": 1,
    "maxFilingsScanned": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("pink_comic/sec-form-144-insider-sales").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "query": "NVIDIA",
  "maxResults": 1,
  "maxFilingsScanned": 10
}' |
apify call pink_comic/sec-form-144-insider-sales --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=pink_comic/sec-form-144-insider-sales",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/W8XApvcWRiafvT1XK/builds/cOjGVByTWSoDYpNgO/openapi.json