SEC 13F Institutional Holdings Tracker: by Filer

Pull SEC Form 13F-HR quarterly holdings for any institutional manager by CIK. One clean row per holding line: CUSIP, issuer name, share class, USD value, shares (or principal), put/call flag, investment discretion, sub-manager attribution, voting authority.

Built for cron (track "what did Berkshire just file?") and for ad-hoc research (pull 8 quarters of Bridgewater for a regime-change analysis). No auth, no scraping: pure SEC EDGAR.

Inputs

{
  "filerCiks": ["1067983", "1350694"],
  "lookbackQuarters": 1,
  "includeAmendments": false
}

input	default	notes
filerCiks	none	Required. List of EDGAR CIKs of the managers. Examples: 1067983 (Berkshire Hathaway), 1350694 (Bridgewater Associates), 1364742 (BlackRock), 1423053 (Citadel Advisors), 1697748 (ARK Investment Management).
lookbackQuarters	1	How many of the most recent 13F-HR filings per filer to pull. 1 = just the latest snapshot.
includeAmendments	false	If true, also pull 13F-HR/A (amendment) filings.
userAgent	(voiddo default)	SEC requires a User-Agent identifying the requester.

Output

One row per <infoTable> line in the 13F. A single holding may appear multiple times if multiple sub-managers (under the same filer umbrella) hold separate blocks: that's how SEC structures the filing and we preserve it (deduplicate downstream if you want a clean per-CUSIP roll-up).

field	example
filerCik	1067983
filerName	BERKSHIRE HATHAWAY INC
filingManager	Berkshire Hathaway Inc
form	13F-HR
accessionNumber	0001193125-26-226661
filingDate	2026-05-15
periodOfReport	03-31-2026
isAmendment	false
nameOfIssuer	APPLE INC
titleOfClass	COM
cusip	037833100
valueUsd	61875000000
shares	300000000
principalAmount	null
shareUnit	SH (or PRN if principal $)
putCall	null, Put, or Call
investmentDiscretion	DFND, SOLE, OTR
votingSole	300000000
votingShared	0
votingNone	0
otherManagerSeqs	["4"]
otherManagerNames	["<sub-manager name as filed>"]
filingUrl	https://www.sec.gov/Archives/edgar/data/1067983/.../0001193125-26-226661-index.htm

Daily / weekly cron pattern

13F filings drop 45 days after each calendar quarter (so May 15, Aug 14, Nov 14, Feb 14). A weekly cron with lookbackQuarters: 1 catches each new filing within days of it being posted.

{ "filerCiks": ["1067983", "1350694", "1423053"], "lookbackQuarters": 1 }

Real-world questions this answers

• Hedge-fund following. What did Berkshire just buy or sell vs. last quarter?
• Smart-money flow. Which 13F filers piled into NVDA last quarter?
• Risk monitoring. Track concentration in a single CUSIP across N filers.
• Manager attribution. A 13F that lists sub-managers (Berkshire's does) names them in otherManagerNames: you see whose desk each position is on.

What it doesn't do

• No 13F-NT (no holdings filings).
• No 13D / 13G (those are a separate filing type for >5% beneficial ownership: different actor).
• No put/call valuation analytics: raw filing data only.
• No automatic delta-vs-prior-quarter computation: pull lookbackQuarters: 2 and diff downstream if you need that.

Pricing

Pay per event. Price per 1,000 events:

Event	Base price	Bronze	Silver	Gold
13F holding extracted	$10.00	$9.00	$8.00	$7.00

Bronze, Silver and Gold are the discounts Apify gives users of its paid plans. The Pricing tab always shows the current prices.

Run it through the API

Python, with the apify-client package:

from apify_client import ApifyClient

client = ApifyClient("<YOUR_APIFY_TOKEN>")
run = client.actor("v0iddo/sec-13f-institutional-holdings").call(run_input={"filerCiks": ["1067983"]})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

JavaScript, with the apify-client package:

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<YOUR_APIFY_TOKEN>' });
const run = await client.actor('v0iddo/sec-13f-institutional-holdings').call({"filerCiks": ["1067983"]});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

One HTTP call that waits for the run and returns the rows (for runs that finish within 5 minutes):

curl -X POST "https://api.apify.com/v2/acts/v0iddo~sec-13f-institutional-holdings/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"filerCiks": ["1067983"]}'

Use it from an agent (MCP)

Claude, Cursor, VS Code and other MCP clients can call this actor as a tool through the Apify MCP server. Add it to the client's MCP configuration:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=v0iddo/sec-13f-institutional-holdings",
      "headers": {
        "Authorization": "Bearer <YOUR_APIFY_TOKEN>"
      }
    }
  }
}

FAQ

Do I need an account, cookies or an API key?

No. The actor reads public data without logging in. You only need an Apify account to start it.

How am I charged?

Pay per event, at the prices on the Pricing tab for your Apify plan (the Pricing section of this page lists them). The platform usage of the run is included in those prices, and your spending limit for a run is always respected.

Why did my run return no results?

The status message and the log of the run say why: usually nothing matched the input, or the source did not answer for a moment. Check the input against the example above and run it again.

Can I run it on a schedule?

Yes. Save your input as a task and add a schedule in the Apify Console (daily, hourly or with a cron expression). Each run gets its own dataset, so you keep a history.

Which formats can I export?

JSON, CSV, Excel, XML, HTML table and RSS from the Output tab or the API. Integrations send the rows to Google Sheets, Slack, Make, Zapier, n8n or a webhook.

Is collecting this data allowed?

The actor collects data that the source publishes openly, without a login. Public data can still be personal data under laws such as the GDPR, and sources have their own terms: make sure your use of the data follows the rules that apply to you.

What happens when the source changes?

An automated test runs the actor every day on the example input and checks the rows, not only that the run finished. When a check fails, the actor is repaired and rebuilt; the build history on this page shows each update.

Something is missing or wrong. Where do I report it?

Open an issue on the Issues tab of this actor with the run link. Requests for a new field are welcome too.

Related actors

• Insider Trades Scraper: SEC EDGAR Form 4 by Ticker
• SEC 13D/13G Beneficial Ownership Filings Scraper
• SEC 8-K Scraper: Material Events by Ticker
• Yahoo Finance Scraper: Stock Quotes and Key Statistics
• FCC ECFS Public Notices & Filings Scraper
• Federal Register Scraper: Rules, Proposed Rules, Notices

Maintained by

vøiddo studio: small independent shop.