# SEC EDGAR Filing Monitor (`titan_coder/sec-edgar-filing-monitor`) Actor

EDGAR scrapers re-list a company's whole filing history on every run. This one remembers what it already delivered and reports only filings that appeared since your last check — 10-K, 10-Q, 8-K, Form 4 insider trades and more. Uses the official free SEC API; quiet days cost nothing.

- **URL**: https://apify.com/titan\_coder/sec-edgar-filing-monitor.md
- **Developed by:** [Radu Furtuna](https://apify.com/titan_coder) (community)
- **Categories:** Business, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$15.00 / 1,000 new filing detecteds

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?

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 EDGAR Filing Monitor

Durable monitor for new SEC filings — 10-K/10-Q annual/quarterly reports, 8-K material events, Form 4
insider trades, and more — on a watchlist of public companies, via the official, free SEC EDGAR Submissions API.

### Why

Investors, analysts, and compliance teams want to know the moment a tracked company files something
material (an 8-K especially — material events are time-sensitive). Existing scrapers on Apify only do a
one-off pull; none durably track what's already been seen and pay only for genuinely new filings.

### How it works

1. You provide **your own contact email** (SEC requires a descriptive User-Agent identifying the requester
   on every request — fair-use policy, not a secret, never shared elsewhere).
2. Each `watch` is one company you track by its SEC Central Index Key (`cik`).
3. Every run fetches the company's most recent filings (EDGAR returns newest first) and diffs them against
   a durable checkpoint of accession numbers already seen for that watch.
4. Genuinely new filings are pushed to the dataset and billed once each (`new-filing-detected`); checking a
   watch with nothing new costs nothing beyond the fixed platform run cost.

### Input

```json
{
  "monitorId": "my-watchlist",
  "userAgentContact": "you@example.com",
  "watches": [
    { "watchId": "apple", "cik": "320193" },
    { "watchId": "microsoft", "cik": "789019" }
  ],
  "notifyOn": "new_alerts",
  "webhookUrl": "https://example.com/webhook"
}
```

Add more watches later under the same `monitorId` — each watch keeps its own independent history.

### Billing

Pay-per-event: `new-filing-detected` — charged only for a filing genuinely new since the previous check of
that watch. The first check of a new watch establishes a baseline (no charge). Failed/blocked checks are
never charged.

#### Delivery guarantee: at-most-once (not exactly-once)

The right to write a row and to charge for it is granted by a single atomic primitive — one
`addRequest(uniqueKey)` into a dedicated, named claim-journal Request Queue
(`<prefix>-<monitorId>-claims`). Exactly one run ever wins that key. Claim requests are never deleted
and never handled: the queue is a permanent journal of irreversible attempts, not a work list.

What this buys you, stated honestly:

- **You will never be charged twice for the same filing.** That is the guarantee.
- **It is not exactly-once.** If a run wins the claim and then dies before the row reaches the
  dataset (or before the charge completes), that filing is *lost*: it closes as `dataset_unknown` /
  `charge_unknown` and is never re-delivered. We deliberately prefer losing a delivery over
  double-charging you.
- **Boundary of the guarantee:** it holds for as long as the named claim-journal queue exists. Anyone
  with account access can delete or re-create that queue through the Apify Console/API; a fresh
  journal starts empty, and previously delivered filings could then be delivered and billed again.
  That is an inherent limit of any durable storage, not a defect of the protocol.
- **Migration boundary:** the guarantee applies from the build that introduced the claim gate onward.
  Older builds of this actor must not keep running against the same `monitorId` — they predate the
  journal and would not see the claims it holds.
- `coverage.claimJournalSize` reports the journal's size each run (best-effort; `null` if the queue's
  metadata could not be read, and the value lags by a few seconds because Apify's
  `totalRequestCount` is eventually consistent). Use it to watch growth, not to make decisions.

#### One-time storage rename in the claim-gate build

Named storages used to be derived from the full actor name (`sec-edgar-filing-monitor`, 24 characters).
With a 40-character `monitorId` that produced a 65-character storage name — over Apify's 63-character
limit, so long `monitorId`s could not work at all. They are now derived from a short prefix
(`sec-edgar`), which keeps every name — including the new `-claims` queue — inside the limit. The
one-time cost: durable checkpoints start empty, so the first run of each watch after this build is a
**baseline**. A baseline delivers no rows and charges nothing, so this cannot cause double billing; you
only lose one delta window.

### Honest limits

- Each check fetches the company's recent filings feed (up to 1,000 most recent, EDGAR's own cap) — new
  filings appear at the top, sufficient for monitoring.
- `seenIds` per watch is capped (FIFO by discovery order); an evicted, then re-surfaced accession number
  can be re-billed — only matters for extremely high-filing-volume companies.
- We don't invent data: if the API response shape changes, or a watch's `cik` is wrong, the run reports it
  honestly instead of silently returning zero results.

Author: OmniCoder (https://t.me/OmniCoder)

# Actor input Schema

## `monitorId` (type: `string`):

Name of this monitor's durable history (a-z, 0-9, dash; up to 40 chars).

## `userAgentContact` (type: `string`):

SEC EDGAR requires an identifiable User-Agent with contact details on every request (fair-use policy). Put YOUR OWN email here, or a contact link. This is not a secret and is sent only to SEC.

## `watches` (type: `array`):

1-30 objects: {"watchId": "apple", "cik": "320193"}. cik is the SEC Central Index Key (find it via the EDGAR full-text search or company search). New companies can be added later under the same monitorId.

## `notifyOn` (type: `string`):

new\_alerts — post the webhook only when new paid filings were delivered; always — post it every run; never — do not call webhookUrl at all.

## `webhookUrl` (type: `string`):

Optional. Receives a digest of delivered (paid) new filings as JSON. HTTPS only.

## Actor input object example

```json
{
  "monitorId": "my-watchlist",
  "userAgentContact": "OmniCoder Apify Actor (https://t.me/OmniCoder)",
  "watches": [
    {
      "watchId": "apple",
      "cik": "320193"
    }
  ],
  "notifyOn": "new_alerts"
}
```

# Actor output Schema

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

Every row this run produced. Key fields: watchId, cik, form, filingDate, accessionNumber.

## `coverage` (type: `string`):

What this run actually covered and what it charged for: per-target status and reason, rows delivered and rows billed. Enough to reconcile every charge against every row.

## `digest` (type: `string`):

A short human-readable summary of what this run found, written every run.

# 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 = {
    "monitorId": "my-watchlist",
    "userAgentContact": "OmniCoder Apify Actor (https://t.me/OmniCoder)",
    "watches": [
        {
            "watchId": "apple",
            "cik": "320193"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("titan_coder/sec-edgar-filing-monitor").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 = {
    "monitorId": "my-watchlist",
    "userAgentContact": "OmniCoder Apify Actor (https://t.me/OmniCoder)",
    "watches": [{
            "watchId": "apple",
            "cik": "320193",
        }],
}

# Run the Actor and wait for it to finish
run = client.actor("titan_coder/sec-edgar-filing-monitor").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 '{
  "monitorId": "my-watchlist",
  "userAgentContact": "OmniCoder Apify Actor (https://t.me/OmniCoder)",
  "watches": [
    {
      "watchId": "apple",
      "cik": "320193"
    }
  ]
}' |
apify call titan_coder/sec-edgar-filing-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,titan_coder/sec-edgar-filing-monitor"
        }
    }
}
```

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/sFeGeJotcpYtbEa2y/builds/ZxaSoJRR6GrGHgvYZ/openapi.json