# SEC EDGAR — Clean Filings & Financials (`clearrecord/sec-edgar-clean-filings-financials`) Actor

Pull structured SEC EDGAR data — company filings, financial statements, and year-over-year changes — clean and ready for analysis, AI pipelines, and RAG workflows. Supports filing history, XBRL financials, and historical pagination.

- **URL**: https://apify.com/clearrecord/sec-edgar-clean-filings-financials.md
- **Developed by:** [Clear Record](https://apify.com/clearrecord) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $10.00 / 1,000 filings lookups

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?

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 EDGAR Financial Filings

Pull clean, structured financial data from SEC EDGAR by ticker or CIK — filings history, XBRL financial statements, and year-over-year changes — ready for analysis, AI pipelines, and RAG workflows.

Data comes directly from SEC's free public API. No scraping, no login required.

\---

\## What it returns

\*\*Filing history\*\* — every SEC submission on record for a company: form type, filing date, report date, accession number, and a direct link to the primary document. Supports all form types (10-K, 10-Q, 8-K, DEF 14A, etc.) with optional filtering. For companies with long histories, optional historical pagination fetches filings older than SEC's default ~1,000-filing window.

\*\*Structured financials\*\* — key financial concepts pulled from XBRL data as a clean time series: revenue, net income, total assets, liabilities, equity, EPS, and cash. Custom concepts supported. Each data point includes fiscal year, fiscal period, form type, start/end dates, and accession number.

\*\*Period-over-period changes\*\* — year-over-year and quarter-over-quarter diffs computed automatically, including absolute change, percent change, and duration-matched comparisons so you're not comparing a full year to a quarter.

\---

\## Inputs

| Field | Type | Default | Description |

|---|---|---|---|

| `identifier` | string | `AAPL` | Ticker symbol or SEC CIK number |

| `fetchFilings` | boolean | `true` | Include filing history |

| `formsFilter` | list | `\[]` | Limit to specific form types, e.g. `\["10-K", "10-Q"]`. Empty = all forms |

| `filingsLimit` | integer | `50` | Max filings to return (1–500), most recent first |

| `fetchFinancials` | boolean | `true` | Include structured XBRL financials |

| `financialConcepts` | list | `\[]` | Custom XBRL concepts to fetch. Empty = standard set |

| `includeHistorical` | boolean | `false` | Fetch filings older than SEC's default ~1,000-filing window (slower) |

\---

\## Output structure

The dataset returns up to three rows per run:

\*\*`summary`\*\* — resolves your identifier to a CIK.

\*\*`filings`\*\* — company metadata plus the full filing list. Each filing includes form type, filing date, report date,

# Actor input Schema

## `identifier` (type: `string`):

Stock ticker (e.g. AAPL) or SEC CIK number.

## `fetchFilings` (type: `boolean`):

List of the company's SEC filings (10-K, 10-Q, 8-K, etc.) with direct links to each document.

## `formsFilter` (type: `array`):

e.g. \["10-K", "10-Q"]. Leave empty to include all forms.

## `filingsLimit` (type: `integer`):

Maximum number of filings to return. Applies to the most recent filings first.

## `fetchFinancials` (type: `boolean`):

Revenue, net income, assets, EPS, etc. as a clean time series pulled from XBRL data.

## `financialConcepts` (type: `array`):

e.g. \["Revenues", "NetIncomeLoss"]. Leave empty to use the standard default set (revenue, net income, assets, liabilities, equity, EPS, cash). Raw values are always returned for any concept SEC reports. Period-over-period change (financial\_changes) for a custom concept is only computed when it's a recognized balance-sheet-type (point-in-time) concept OR a normal duration concept with real period dates attached. A concept with SOME usable data but nothing comparable (e.g. only one period ever reported, or its latest period is currently ambiguous in SEC's own data) is reported under financial\_changes.diffs\[concept].incomplete\_series with a stated reason — concepts\_with\_insufficient\_history is reserved for a concept with no usable observations at all.

## `includeHistorical` (type: `boolean`):

SEC's submissions API only returns roughly the newest ~1,000 filings by default under 'recent'. For companies with a long filing history, older filings are paginated into separate files. Enabling this fetches those too (slower, extra requests).

## Actor input object example

```json
{
  "identifier": "AAPL",
  "fetchFilings": true,
  "formsFilter": [],
  "filingsLimit": 50,
  "fetchFinancials": true,
  "financialConcepts": [],
  "includeHistorical": false
}
```

# Actor output Schema

## `result_type` (type: `string`):

Type of result row: summary, filings, financials, or error variant.

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

SEC CIK number for the company.

## `filings` (type: `string`):

Filing history including form type, dates, and document URLs.

## `financials` (type: `string`):

Structured XBRL financial time series.

## `financial_changes` (type: `string`):

Period-over-period diffs including percent change and comparison type.

# 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 = {
    "identifier": "AAPL"
};

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

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

```

## MCP server setup

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

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/s89ae206gy5sn0p3b/builds/NBeiCfvGJMnQMNJ2V/openapi.json