# SEC 13F Institutional Holdings Tracker (`m_ctim/sec-13f-institutional-holdings-tracker`) Actor

Track new SEC Form 13F-HR filings, the quarterly disclosure large institutional investment managers must file listing their U.S. equity holdings. Search by manager name or a company they might hold.

- **URL**: https://apify.com/m\_ctim/sec-13f-institutional-holdings-tracker.md
- **Developed by:** [Timothy Kelvin](https://apify.com/m_ctim) (community)
- **Categories:** Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-usage

## 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 13F Institutional Holdings Tracker

Track new SEC Form 13F-HR filings — the quarterly disclosure every
institutional investment manager with $100M+ in U.S. equities must file,
listing what they hold.

Built for anyone doing "whale watching": tracking what big funds are
buying, spotting a new filer, or checking who else holds a stock you're
watching.

### Input

```json
{
  "keyword": "Berkshire Hathaway",
  "daysBack": 45,
  "maxResults": 50
}
```

| Field | Type | Description |
|---|---|---|
| `keyword` | string (optional) | Free-text search across the filing. Matches both the manager's own name **and** any company named in their reported holdings — searching `"Apple"` surfaces managers who hold Apple stock, not just companies named Apple. Leave blank for all new 13F filings market-wide. |
| `daysBack` | number | How many days back from today to search, by filing date. Default `45`, max `120`. 13F filings cluster around the 45-day-after-quarter-end deadline, so a wider window catches more filers. |
| `maxResults` | number | Max filings to return, most recently filed first. Default `50`, max `100`. |

### Output

One record per filing:

```json
{
  "accessionNumber": "0002150492-26-000004",
  "filerName": "BERKSHIRE HATHAWAY INC",
  "filerCik": "0001067983",
  "filerTickers": "BRK-A, BRK-B",
  "filingDate": "2026-08-14",
  "periodOfReport": "2026-06-30",
  "filingUrl": "https://www.sec.gov/Archives/edgar/data/1067983/000215049226000004-index.htm"
}
```

A search with no matches in the requested window returns no items but
is still billed once for the search.

### How it works

Direct calls to the official [SEC EDGAR full text search
API](https://www.sec.gov/edgar/search/) (`efts.sec.gov`), filtered to
Form 13F-HR filings. No proxy, no key, no scraping.

**Note:** 13F filings are two documents — a cover page (what this actor
indexes) and a separate "information table" listing the actual security
positions, share counts, and values. This actor tells you *who just
filed* and *when*; use `filingUrl` to open the full filing for the
line-by-line holdings.

### Pricing note

Billed per **search**, not per filing returned — one charge whether the
search returns 0 filings or 100.

### Related products

- [SEC 13D/13G Ownership Tracker](https://github.com/timmKal01/sec-13d-ownership-tracker) — 5%+ activist/passive stakes in a single company, rather than a manager's full portfolio
- [Insider Trading Alert](https://github.com/timmKal01/insider-trading-alert) — the officer/director equivalent (SEC Form 4)

# Actor input Schema

## `keyword` (type: `string`):

Free-text search across the filing, which matches both the filing manager's name (e.g. "Berkshire Hathaway") and any company named in their reported holdings (e.g. searching "Apple" surfaces managers who hold Apple stock). Leave blank for all new 13F filings market-wide.

## `daysBack` (type: `integer`):

How many days back from today to search, by filing date. 13F filings are quarterly and cluster around the 45-day-after-quarter-end deadline, so a wider window catches more filers.

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

Maximum number of filings to return, most recently filed first.

## Actor input object example

```json
{
  "daysBack": 45,
  "maxResults": 50
}
```

# Actor output Schema

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

// Run the Actor and wait for it to finish
const run = await client.actor("m_ctim/sec-13f-institutional-holdings-tracker").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("m_ctim/sec-13f-institutional-holdings-tracker").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 m_ctim/sec-13f-institutional-holdings-tracker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,m_ctim/sec-13f-institutional-holdings-tracker"
        }
    }
}

```

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/iBuVVrTvbQdgoxHnE/builds/i1cV0fXrGz97vuCeS/openapi.json