algoum API documentation

The algoum API turns the filings that US companies and investment managers submit to the SEC (U.S. Securities and Exchange Commission) through EDGAR into clean, consistent JSON. One key, one base URL, the same response shape everywhere - whether the data ends up in a dashboard or in an algo trading strategy.

What you can query

Insider transactions
Buys and sells reported by a company’s own officers, directors and large owners, with the signals derived from them (SEC Forms 4, 5, 4/A and 5/A).
Material events
The events a company must disclose - leadership changes, mergers, bankruptcies, cyber incidents - as history, feed or live stream (SEC Forms 8-K, 8-K/A, NT 10-K and NT 10-Q).
Institutional holdings
Quarterly portfolios of institutional investors and the aggregated picture per stock (SEC Forms 13F-HR, 13F-HR/A and 13F-NT).

Shared helpers resolve tickers to company identifiers, return the original filing behind every record, and report how fresh each data source is.

How to read these pages

The endpoint reference is generated from the API’s own OpenAPI specification, so it describes the endpoints exactly as they answer right now. The guides around it explain the parts that span all endpoints. To send real requests against your own key, use Swagger UI: it renders the same specification with a built-in request form.

Using algoum from an AI assistant

The same data is available to AI assistants such as Claude, GitHub Copilot and Cursor through the API’s MCP server, with the same key. The MCP page shows the setup for each assistant; the setup guide is also public at fi4all/algoum-mcp.