> ## 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/factors/exposures

> Return compact security, portfolio, or watchlist factor exposures with optional diagnostics and provenance

Return compact security, portfolio, or watchlist factor exposures with optional diagnostics and provenance

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

## Canonical metadata

* `requestId`
* `traceparent`

## 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/factors/exposures"
  ```
</RequestExample>

## Example response

<ResponseExample>
  ```json theme={null}
  {
    "object": "list",
    "data": [
      {
        "object": "factor_exposure",
        "id": "factor_exposure:AAPL:VALUE:2026-06-09",
        "subjectType": "security",
        "subjectKey": "AAPL",
        "factorKey": "VALUE",
        "beta": -0.42,
        "percentile": 18.2,
        "confidence": "high",
        "modelName": "secapi_stock_basket_factor_model_v1",
        "asOf": "2026-06-09T22:15:00.000Z",
        "responseMode": "compact",
        "expansionHints": [
          "Use include=diagnostics or response_mode=standard for regression diagnostics such as rSquared, tStat, and observationCount."
        ]
      }
    ],
    "hasMore": false,
    "nextCursor": null,
    "responseMode": "compact",
    "requestId": "req_2ZK8Q1W9F4M6P7R3",
    "traceparent": "00-4bf92f3577b34da6a3ce929d0e0e4736-00f067aa0ba902b7-01"
  }
  ```
</ResponseExample>

## Give this prompt to your agent

<Prompt>
  Use SEC API GET /v1/factors/exposures to return compact security, portfolio, or watchlist factor exposures with optional diagnostics and provenance. Preserve `requestId`, `traceparent` 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