# SEC EDGAR Filings API — Official Source, No API Key (`nexgendata/sec-edgar-filings-api`) Actor

Official U.S. SEC EDGAR filings in one API. Pick a filing type — Form D, Form 4 insider trades, 8-K, 13F holdings, 13D/G, S-1/IPO, ADV, NPORT, XBRL and 20+ more — and get clean structured records by ticker, company, CIK or date. Official source. No API key. Pay per record.

- **URL**: https://apify.com/nexgendata/sec-edgar-filings-api.md
- **Developed by:** [NexGenData](https://apify.com/nexgendata) (community)
- **Categories:** Other
- **Stats:** 13 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$50.00 / 1,000 ad extracteds

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 EDGAR Filings API — one call, 25+ filing types

Pull clean, structured **U.S. SEC EDGAR** filings without learning EDGAR's
full-text search, CIK lookups, or form quirks. Choose a `filing_type`, add an
optional ticker, company, or date window, and get back normalized records
ready for a spreadsheet, database, or model.

### What you can pull

Set **`filing_type`** to any of these. Each routes to a dedicated, maintained
EDGAR extractor:

| Filing type | Underlying extractor |
|---|---|
| Form D | [`sec-form-d-scraper`](https://apify.com/nexgendata/sec-form-d-scraper) |
| Form 4 | [`sec-form4-insider-tracker`](https://apify.com/nexgendata/sec-form4-insider-tracker) |
| 8-K | [`sec-form-8k-material-events-scraper`](https://apify.com/nexgendata/sec-form-8k-material-events-scraper) |
| 13F | [`sec-form-13f-tracker-pro`](https://apify.com/nexgendata/sec-form-13f-tracker-pro) |
| ADV | [`sec-form-adv-investment-adviser-tracker`](https://apify.com/nexgendata/sec-form-adv-investment-adviser-tracker) |
| NPORT | [`sec-form-nport-p-mutual-fund-holdings`](https://apify.com/nexgendata/sec-form-nport-p-mutual-fund-holdings) |
| NPX | [`sec-form-npx-mutual-fund-proxy-votes`](https://apify.com/nexgendata/sec-form-npx-mutual-fund-proxy-votes) |
| 13D/G | [`sec-schedule-13dg-activist-tracker`](https://apify.com/nexgendata/sec-schedule-13dg-activist-tracker) |
| 144 | [`sec-form-144-restricted-stock-sales-tracker`](https://apify.com/nexgendata/sec-form-144-restricted-stock-sales-tracker) |
| 11-K | [`sec-form-11-k-employee-stock-plan-tracker`](https://apify.com/nexgendata/sec-form-11-k-employee-stock-plan-tracker) |
| NT | [`sec-form-nt-late-filing-tracker`](https://apify.com/nexgendata/sec-form-nt-late-filing-tracker) |
| Reg A+ | [`sec-reg-a-plus-crowdfunding-offerings-tracker`](https://apify.com/nexgendata/sec-reg-a-plus-crowdfunding-offerings-tracker) |
| IPO/S-1 | [`sec-ipo-prospectus-tracker`](https://apify.com/nexgendata/sec-ipo-prospectus-tracker) |
| comment letters | [`sec-comment-letter-monitor`](https://apify.com/nexgendata/sec-comment-letter-monitor) |
| litigation releases | [`sec-litigation-releases`](https://apify.com/nexgendata/sec-litigation-releases) |
| delistings | [`sec-delisting-deregistration-tracker`](https://apify.com/nexgendata/sec-delisting-deregistration-tracker) |
| exec comp | [`sec-exec-comp-proxy-tracker`](https://apify.com/nexgendata/sec-exec-comp-proxy-tracker) |
| XBRL frames | [`sec-xbrl-financial-frames`](https://apify.com/nexgendata/sec-xbrl-financial-frames) |

### Example input

```json
{
  "filing_type": "8-K",
  "ticker": "AAPL",
  "dateFrom": "2026-06-01",
  "dateTo": "2026-06-30",
  "limit": 25
}
```

Leave the dates out and you get the last 60 days. Use **`moduleInput`** to pass
any advanced field straight through to the underlying extractor.

#### Controlling volume and cost

Some filing types return **many records per filing** — a single 13F or NPORT
filing carries hundreds of holdings. To keep a run predictable, the
**`max_records`** field (or **`limit`**, if `max_records` is not set) caps the
number of records actually **delivered and billed**, across every filing type.
For example, `filing_type: "NPORT"` with `max_records: 25` returns at most 25
records and bills at most 25 — never the full holdings expansion. If neither
field is set, a run defaults to **25 records**. You are only ever charged for
records delivered, up to this cap.

### Output

Every filing is pushed as one record to the run's dataset, with a
`_filing_type` tag so mixed pulls stay sortable. Export to JSON, CSV, or Excel,
or read it over the API.

### Pricing

Pay only for what you get — **pay-per-event**, no monthly fee.

| Event | Price | When |
|---|---|---|
| Filing record | $0.05 | Charged once per delivered filing record. Empty or blocked queries cost nothing. |

You are billed exactly once per record returned. If a query returns no
filings, or the source is temporarily unavailable, you are not charged.

### Notes

- Read-only. This actor calls specialist SEC extractors and re-emits their
  records; it never modifies them.
- Data originates from public SEC EDGAR filings.

# Actor input Schema

## `filing_type` (type: `string`):

Which SEC filing type to pull. Each routes to a dedicated EDGAR extractor.

## `ticker` (type: `string`):

Optional. Filter to a company by ticker (e.g. AAPL). Applied where the filing type supports it.

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

Optional. Company name or keyword to search within the chosen filing type.

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

Optional. Start of the filing date window. Defaults to the last 60 days.

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

Optional. End of the filing date window. Defaults to today.

## `limit` (type: `integer`):

Optional. Caps the number of records DELIVERED and BILLED (fallback if max\_records is not set). Defaults to 25.

## `max_records` (type: `integer`):

Optional hard cap on records delivered and billed, across every filing type. When set, OVERRIDES limit. Leave empty to let limit control the cap. Prevents a single 13F/NPORT filing (hundreds of holdings) from billing far more than expected.

## `moduleInput` (type: `object`):

Optional. Power-user passthrough: keys here are forwarded verbatim to the underlying filing-type actor, overriding the generic fields above.

## Actor input object example

```json
{
  "filing_type": "Form D",
  "limit": 25
}
```

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgendata/sec-edgar-filings-api").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("nexgendata/sec-edgar-filings-api").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 '{}' |
apify call nexgendata/sec-edgar-filings-api --silent --output-dataset

```

## MCP server setup

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

```

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/0PFsldghMoEZU3r1c/builds/crhHRNf1JAFq5xOFN/openapi.json