Skip to main content
Special Situations is the authenticated API for following filing-derived M&A, tender offers, going-private transactions, spin-offs, activist campaigns, restructurings, and bankruptcies. Use it to monitor the current record and its filing trail while keeping current situations, calendar events, and immutable weekly digest snapshots distinct.

​
Free public preview

The /v1/embed/situations routes are a free, anonymous preview for public sites and browser embeds. Do not send x-api-key to these routes:
Preview reads are CORS-enabled for browser use and return public cache headers. They are intentionally limited to a capped, recent public projection, so a cached response is not a substitute for an authenticated research workflow. To move beyond the preview, create an organization API key and call the /v1/situations routes from your server, worker, shell, SDK, CLI, or MCP client. Never put a paid API key in browser-delivered code.

​
Find a current event and its filing trail

Narrow list results by type, subtype, status, ticker, sector, market-cap bucket, country, announcement date, update time, and supported EDGAR forms. Use the returned situation ID to fetch current detail, its paginated filing timeline, a compact summary, a Markdown export, or an underwriting pack. Record filing identities, source references, update metadata, and requestId for a decision-critical record.

​
Routes for discovery, monitoring, and evidence

Use enrich=false to request a smaller list projection when scanning a wide set. It changes the returned projection, not the billed request class. limit is 1 through 100; advance pagination only with the returned cursor and unchanged filters. CLI and MCP workflows use the structured JSON feed (/v1/situations/feed) so agents can preserve IDs, request metadata, and citations; RSS is a direct HTTP/feed-reader surface at /v1/situations/feed.rss.

​
Freshness, coverage, and decision boundaries

Situations are filing-derived. They do not confirm that a transaction will close or that a disclosed date, term, or status remains current. Digest issues are immutable publication-time snapshots, while current situation detail can change as new filings arrive. Calendar and performance responses answer different questions and should remain separate from current detail in a research record. The authenticated API is distinct from public embed routes, and the paid RSS feed is distinct from the limited public website RSS preview. Watchlist filters can be created with API-key credentials, while email or organization webhook/stream delivery requires bearer/org authentication and is metered as monitor management plus delivery events. Coverage is limited to SEC filing-derived situations. A missing situation or timeline is not proof that no related event exists.

​
Next action

Fetch the selected situation’s filing timeline and inspect the original SEC filing for each term or date used in a decision. Use the source-cited export to hand the record to an analyst or agent.