SEC Form N-PX Tracker — Mutual Fund Proxy Votes
Pricing
from $50.00 / 1,000 proxy vote records
Track N-PX mutual-fund proxy votes from SEC EDGAR — parsed, source-linked JSON for analysts, funds and AI agents.
Pricing
from $50.00 / 1,000 proxy vote records
Rating
0.0
(0)
Developer
NexGenData
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
5 days ago
Last modified
Categories
Share
Which slice of Form N-PX filings to scan. recent_filings walks all N-PX submissions in the last daysBack days. by_cik pulls every N-PX filing for a specific fund CIK. by_issuer extracts every vote across all funds that mentions a specific issuer (ticker or company-name substring).
Look at N-PX filings filed within the last N days. Only used when mode=recent_filings. Note: most N-PX filings are filed July through September each year for the annual period ending June 30, so a 30-day window outside that range may return zero results.
SEC CIK (Central Index Key) of the fund / fund-family. Required when mode=by_cik. Example: 1120925 for T. Rowe Price International Index Fund. Look up CIK at https://www.sec.gov/cgi-bin/browse-edgar.
Issuer the funds voted on. Accepts a US ticker (e.g. AAPL, XOM) or a company-name substring (e.g. Apple, Exxon). Required when mode=by_issuer. The match is case-insensitive and looks for the token inside the N-PX issuer_name field.
Hard cap on total vote records pushed to the dataset (and metered for billing). A single mid-size fund can produce 10,000+ records, and a fund-family annual filing can exceed 1,000,000 records — set this to control cost.
Apify proxy configuration. SEC EDGAR has a polite 10 req/sec rate limit and a User-Agent requirement (we use NexGenData/1.0 contact@thenextgennexus.com). Residential proxy is recommended for sustained throughput.
{ "useApifyProxy": true, "apifyProxyGroups": [ "RESIDENTIAL" ]}