GET /v1/filings/{accession_number}/export

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

{
  "requestId": "req_2ZK8Q1W9F4M6P7R3",
  "provenance": {
    "source": "sec",
    "accessionNumber": "0000320193-25-000079",
    "filingUrl": "https://www.sec.gov/Archives/edgar/data/320193/000032019325000079/aapl-20250927_htm.xml",
    "retrievedAt": "2026-03-17T00:00:00.000Z",
    "parserVersion": "2026-03-13.5",
    "rawSourceKey": "0000320193-25-000079"
  },
  "freshness": {
    "status": "fresh",
    "asOf": "2026-03-17T00:00:00.000Z",
    "sourcePublishedAt": "2025-10-31T00:00:00.000Z",
    "lagMs": 900000
  },
  "materialization": {
    "parserVersion": "2026-03-13.5",
    "materializationVersion": "datastream-3.0"
  }
}

Export one filing in JSON or document formats

Audience: application and coding agent.

Coverage and source scope

Export a selected filing as JSON by default, or request a derived Markdown, CSV, XLSX, DOCX, or PDF document with format. JSON returns the filing manifest; derived formats can be large and should retain the filing accession and source provenance. Derived exports do not replace the original filing as evidence.

Export format and source limits

The optional format parameter defaults to json, which returns a structured filing record. Markdown, CSV, XLSX, DOCX, and PDF are derived exports and can be large; retain the accession number, filing date, and source URL alongside any downstream file. For a smaller evidence workflow, use section extraction instead of exporting an entire filing. An export failure is not a finding about the filing. Use the original SEC filing when exact filing presentation, exhibits, or formatting matters.

Response size

Exports are intentionally full-fidelity and can be large, especially for Markdown, DOCX, PDF, and spreadsheet formats. For agent workflows, prefer section search or direct section extraction with view=agent unless a downstream file or archival workflow needs the complete export.

Canonical metadata

requestId
traceparent
provenance
freshness
materialization

Example request

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

Example response

{
  "requestId": "req_2ZK8Q1W9F4M6P7R3",
  "provenance": {
    "source": "sec",
    "accessionNumber": "0000320193-25-000079",
    "filingUrl": "https://www.sec.gov/Archives/edgar/data/320193/000032019325000079/aapl-20250927_htm.xml",
    "retrievedAt": "2026-03-17T00:00:00.000Z",
    "parserVersion": "2026-03-13.5",
    "rawSourceKey": "0000320193-25-000079"
  },
  "freshness": {
    "status": "fresh",
    "asOf": "2026-03-17T00:00:00.000Z",
    "sourcePublishedAt": "2025-10-31T00:00:00.000Z",
    "lagMs": 900000
  },
  "materialization": {
    "parserVersion": "2026-03-13.5",
    "materializationVersion": "datastream-3.0"
  }
}

Give this prompt to your agent

Failure posture

treat non-2xx responses as contract-aware failures, not free-form errors
preserve requestId and traceparent in logs and downstream reports
if provenance or freshness metadata is present, return it unchanged so trust is not lost in the handoff

​Coverage and source scope

​Export format and source limits

​Response size

​Canonical metadata

​Example request

​Example response

​Give this prompt to your agent

​Failure posture

Coverage and source scope

Export format and source limits

Response size

Canonical metadata

Example request

Example response

Give this prompt to your agent

Failure posture