GET /v1/companies/cash-flow-statements

curl -X GET \
  -H "x-api-key: $SECAPI_API_KEY" \
  -H "secapi-version: 2026-03-19" \
  "https://api.secapi.ai/v1/companies/cash-flow-statements?ticker=AAPL"

{
  "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"
  },
  "traceparent": "00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01"
}

Retrieve an issuer’s SEC-derived cash flow statement history with normalized cash-generation fields

Audience: application and coding agent.

Coverage and source scope

Use this route to review operating, investing, and financing cash-flow history for one issuer. Choose annual or quarterly cadence before comparing periods, because cash-flow rows describe a duration rather than a point-in-time balance. Values are normalized from supported SEC XBRL filings and retain units, periods, and provenance; free-cash-flow fields are derived from those filings, not a forecast. See statements reference and freshness and source evidence.

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/companies/cash-flow-statements?ticker=AAPL"

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"
  },
  "traceparent": "00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01"
}

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

​Canonical metadata

​Example request

​Example response

​Give this prompt to your agent

​Failure posture

Coverage and source scope

Canonical metadata

Example request

Example response

Give this prompt to your agent

Failure posture