Skip to main content
Render one situation as a source-cited Markdown brief for downstream LLM and agent workflows. The export includes the situation headline, lifecycle state, structured deal terms and key dates, filing timeline, accession numbers, and EDGAR source links.
Audience: application and coding agent. This is an authenticated, paid API read. The response is Markdown, not a JSON envelope.

​
Canonical metadata

  • Content-Type: text/markdown; charset=utf-8
  • SECAPI-Meter-Class: situations_export
  • Request-Id
  • traceparent

​
Example request

curl -X GET \
  -H "x-api-key: $SECAPI_API_KEY" \
  -H "secapi-version: 2026-03-19" \
  "https://api.secapi.ai/v1/situations/sit_example_123/export"

​
Example response

# Acme Corp (ACME) - merger/definitive [pending]
Source: SEC API (secapi.ai) - situation sit_example_123 - retrieved 2026-07-10T12:00:00.000Z

## Terms
- Counterparty: Example Holdings - Deal value: $5.00B - Consideration: cash - Premium: 28.5%

## Key dates
- Announced 2026-07-08 - Record - Vote - Expected close 2026-12-31

## Timeline
- 2026-07-08 - 8-K (0001193125-26-000001): Definitive merger agreement filed
  https://www.sec.gov/Archives/edgar/data/1234567/000119312526000001/doc.htm

## Citations
- 0001193125-26-000001 - https://www.sec.gov/cgi-bin/browse-edgar?action=getcompany&type=&dateb=&owner=include&count=40&search_text=000119312526000001

​
Usage and limits

The export is metered separately from normal situation lookups so usage and plan limits can distinguish Copy-for-LLM exports from list and detail reads. It currently uses the standard-read pricing family; plan-level rates may change independently of the route contract.

​
Give this prompt to your agent

​
Failure posture

  • treat 404 as an unknown or unavailable situation ID; do not invent a brief
  • preserve the error code and entitlement context for 402 or 403 responses
  • retry 429 and 5xx responses with bounded backoff, retaining the Request-Id and traceparent headers for support
  • treat absent deal terms, dates, or market values as unknown; do not infer them from prose
  • use the paid detail or filings endpoints when a machine-readable JSON timeline is required