> ## Documentation Index
> Fetch the complete documentation index at: https://docs.secapi.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# GET /v1/statements/segmented-facts

> Return filing-derived segmented fact history for supported metrics such as revenue and segment profit/loss, with product or geography dimensions, hierarchy…

Return filing-derived segmented fact history for supported metrics such as revenue and segment profit/loss, with product or geography dimensions, hierarchy metadata, capability state, and trace references when issuers disclose them

<Info>
  Audience: application and coding agent.
</Info>

## Canonical metadata

* `requestId`
* `traceparent`
* `provenance`
* `freshness`
* `materialization`

## Example request

<RequestExample>
  ```bash theme={null}
  curl -X GET \
    -H "x-api-key: $SECAPI_API_KEY" \
    -H "secapi-version: 2026-03-19" \
    "https://api.secapi.ai/v1/statements/segmented-facts?ticker=AAPL&metric=revenue&period=annual"
  ```
</RequestExample>

## Example response

<ResponseExample>
  ```json theme={null}
  {
    "object": "segmented_fact_series",
    "id": "segfact_cent_jpm_profit_loss_product",
    "createdAt": "2026-03-17T00:00:00.000Z",
    "livemode": true,
    "entityId": "cent_jpm_example",
    "ticker": "JPM",
    "companyName": "JPMorgan Chase & Co.",
    "period": "quarterly",
    "metric": "profit_loss",
    "capability": "supported",
    "records": [
      {
        "segmentAxis": "us-gaap:StatementBusinessSegmentsAxis",
        "segmentMember": "jpm:ConsumerAndCommunityBankingMember",
        "segmentLabel": "Consumer & Community Banking",
        "segmentType": "product",
        "axisFamily": "business",
        "hierarchyDepth": 1,
        "isMostGranularSibling": true,
        "metricKey": "profit_loss",
        "taxonomy": "us-gaap",
        "tag": "ProfitLoss",
        "unit": "USD",
        "value": 4579000000,
        "periodStart": "2026-01-01",
        "periodEnd": "2026-03-31",
        "filingDate": "2026-04-12",
        "reportDate": "2026-03-31",
        "form": "10-Q",
        "accessionNumber": "0000019617-26-000123",
        "capability": "supported",
        "provenance": {
          "source": "sec",
          "accessionNumber": "0000019617-26-000123",
          "filingUrl": "https://www.sec.gov/Archives/edgar/data/19617/000001961726000123/jpm-20260331.htm",
          "retrievedAt": "2026-04-12T00:00:00.000Z",
          "parserVersion": "secapi-segmented-statements-v1"
        }
      }
    ],
    "provenance": {
      "source": "sec",
      "accessionNumber": "0000019617-26-000123",
      "filingUrl": "https://www.sec.gov/Archives/edgar/data/19617/000001961726000123/jpm-20260331.htm",
      "retrievedAt": "2026-04-12T00:00:00.000Z",
      "parserVersion": "secapi-segmented-statements-v1"
    },
    "requestId": "req_2ZK8Q1W9F4M6P7R3"
  }
  ```
</ResponseExample>

## Give this prompt to your agent

<Prompt>
  Use SEC API GET /v1/statements/segmented-facts to return filing-derived segmented fact history for supported metrics such as revenue and segment profit/loss, with product or geography dimensions, hierarchy metadata, capability state, and trace references when issuers disclose them. Preserve `requestId`, `traceparent`, `provenance`, `freshness`, `materialization` in the output. Return a concise markdown summary plus the exact structured payload fields that a downstream engineer or agent should keep using this result.
</Prompt>

## 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