The public Situations database is a free, recent, rate-limited research and discovery surface. This API family is the paid, authenticated product: it unlocks the complete archive, higher limits, source-cited Copy-for-LLM exports, and application or agent workflows.
Why use this
A special situation is not a single filing — it is a durable, evolving object that accretes filings over weeks or months. The SEC API Special Situations surface stitches the triggering and follow-on filings into one situation with a stablesituation_id, a lifecycle status, and a timeline, so agents and applications never have to reassemble a deal from raw EDGAR events.
- Durable situations — one object per deal, with a stable
situation_idthat survives across follow-on filings - Lifecycle status — announced, pending, completed, terminated, and related states, so deal risk is legible at a glance
- Browse by EDGAR form — resolve “what did this
SC 13D/SC TO-T/425/DEFM14Afiling trigger?” directly, with the form expanded to the situation types it drives - Per-filing timeline — the ordered filing history behind each situation, available inline or as a paginated sub-resource
- Enriched or stripped — request the full projection, or the lean stripped shape for wide scans (billed identically)
- Agent-ready evidence — carry issuer identifiers, source filings, freshness metadata, field availability, and machine-readable lifecycle fields through the same workflow
Quick start
Enriched vs. stripped
Every situation list and detail endpoint acceptsenrich:
enrich=true(default) returns the full projection — deal terms, market snapshot, and timeline context.enrich=falsereturns the minimal stripped projection: identity, status, and key dates only.
enrich=false only to reduce payload size on wide scans, never to save quota.
Browse by form
When you already have an EDGAR form in hand and want the situations it opened or advanced, use the by-form endpoint. The form is expanded server-side to the situation types it triggers. URL-encode the form (a space becomes%20):
statuses, tickers, and enrich. Common triggering forms include SC 13D (activist stake), SC TO-T (third-party tender offer), 425 (merger communications), and DEFM14A (merger proxy).
The filing timeline
Each situation carries an ordered, oldest-first timeline of the filings that built it. Fetch it inline with the situation, or page it as a standalone sub-resource:Compact summary
When you need the headline — rendered markdown, deal terms, and the latest timeline event — without the full timeline, use the summary sub-resource:Copy for an LLM, without losing provenance
Use the Markdown export when an agent needs a concise underwriting-ready brief rather than a wide JSON object. It preserves source filing links, accession numbers, dates, and explicitly absent fields. Treat it as evidence to inspect, never as an investment recommendation.Endpoints
| Endpoint | Description |
|---|---|
GET /v1/situations | List situations; filter by types, statuses, tickers, forms, enrich |
GET /v1/situations/feed | Reverse-chronological feed of situation events |
GET /v1/situations/calendar | Upcoming key dates (record, vote, expiry, expected close) |
GET /v1/situations/stats | Counts by type, status, sector, and market-cap bucket |
GET /v1/situations/performance | Closed-situation outcome cohorts |
GET /v1/situations/by-form/{form} | Situations opened or advanced by an EDGAR form |
GET /v1/situations/{situation_id} | One situation with its full per-filing timeline |
GET /v1/situations/{situation_id}/filings | Paginated per-filing timeline |
GET /v1/situations/{situation_id}/summary | Compact summary: markdown, deal terms, latest event |
GET /v1/situations/{situation_id}/export | Source-cited Markdown Copy-for-LLM brief |
SDK and CLI
Thesecapi CLI mirrors the plane:
client.situations:

