Parsing SEC Ownership Filings Form 4 and 13F Into an API
Discover the lessons learned building EdgarFeed, a normalized API that turns SEC EDGAR ownership filing data into clean JSON.
Stock photo for illustration only, not from the actual event
- EDGAR is the SEC's free public filing system, but its raw format is unfriendly for software development.
- Form 4 and 13F are both ownership filings, yet they possess completely different document structures.
- EdgarFeed was built to normalize these raw filings into clean, structured JSON data.
- A live demo with real data is currently available for users to test during the beta phase.
If you have ever needed insider-trade or institutional-holdings data, you have likely encountered EDGAR. It is the SEC's public filing system, it is free, and it contains everything — which happens to be the exact problem. The raw surface was built strictly for regulatory compliance, not for software integration.
This post serves as a short field guide detailing what was learned while building a small API designed to normalize SEC ownership filings. Much of the knowledge shared is general enough that you can apply it even if you never touch their specific tool.
Transforming raw regulatory data from government bodies like the SEC into a clean, normalized API is a major hurdle in FinTech. Because legal documents often feature complex and inconsistent schemas, understanding distinct filing structures like Form 4 and 13F is a vital prerequisite for developers building financial analysis tools.
While both documents qualify as ownership filings, they feature structurally distinct layouts that create significant friction for developers attempting to parse and process them programmatically.
Stock photo for illustration only, not from the actual event
To tackle this challenge, the team created EdgarFeed, a lightweight API that serves normalized ownership filing data as clean JSON. The project is currently running as an open beta:
Developers and interested users can test out the live demo using real data at edgarfeed.onrender.com. The creators are actively welcoming questions regarding their approach and feedback on the API shape, which is the primary goal of the beta release.
Source: Dev.to
Found something wrong in this article? Report an issue with this article
Comments
Leave a Comment