> ## 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/filings/latest/risk-categories

> Classify Item 1A risk categories in a selected issuer filing

Classify Item 1A risk categories in a selected issuer filing

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

## Coverage and source scope

Return deterministic risk-category coverage derived from Item 1A in a selected covered filing. Use one issuer selector and optionally an accession number to make the filing explicit. Categories describe available extracted disclosure and should be verified against the cited filing before an investment conclusion.

## Coverage and interpretation

Use one issuer selector, and pass `accession_number` when the review must remain tied to a known filing. Categories are deterministic labels over available Item 1A extraction, not a risk score, completeness guarantee, or investment conclusion. Keep the cited accession and read the underlying risk-factor language before reporting a category. See [risk factors](/glossary/risk-factors) for the filing context.

## Canonical metadata

* `requestId`
* `traceparent`
* `provenance`
* `freshness`
* `materialization`
* `capability`
* `statusNote`

## 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/filings/latest/risk-categories"
  ```
</RequestExample>

## Example response

<ResponseExample>
  ```json theme={null}
  {
    "object": "risk_category_report",
    "id": "riskcat_000078901926000001",
    "createdAt": "2026-03-18T16:00:00.000Z",
    "livemode": false,
    "entityId": "ent_msft",
    "ticker": "MSFT",
    "companyName": "Microsoft Corporation",
    "form": "10-K",
    "filingDate": "2026-01-28",
    "reportDate": "2025-12-31",
    "accessionNumber": "0000789019-26-000001",
    "sectionKey": "item_1a",
    "capability": "supported",
    "statusNote": null,
    "categoryCount": 3,
    "categories": [
      {
        "key": "cybersecurity_privacy",
        "label": "Cybersecurity and data privacy",
        "confidence": "high",
        "mentionCount": 2,
        "signals": [
          "cybersecurity",
          "data breach",
          "privacy"
        ],
        "snippets": [
          "Cybersecurity threats, ransomware, data breaches, and other information security incidents could disrupt our platform and expose us to privacy law liability."
        ]
      }
    ],
    "summaryMd": "## Risk-category coverage for Microsoft Corporation\n\nLatest filing date: 2026-01-28. Top categories: Cybersecurity and data privacy (high), Competition and market structure (medium), Macroeconomic and demand conditions (medium). The report is supported and exposes the dominant risk themes found in the current Item 1A disclosure.",
    "provenance": {
      "source": "sec",
      "accessionNumber": "0000789019-26-000001",
      "filingUrl": "https://www.sec.gov/Archives/example.htm",
      "acceptedAt": "2026-01-28T21:00:00.000Z",
      "retrievedAt": "2026-03-18T16:00:00.000Z",
      "parserVersion": "2026-03-18.1"
    },
    "freshness": {
      "status": "fresh",
      "asOf": "2026-03-18T16:00:00.000Z",
      "sourcePublishedAt": "2026-01-28T21:00:00.000Z",
      "lagMs": 0
    },
    "materialization": {
      "parserVersion": "2026-03-18.1",
      "materializationVersion": "2026-03-18.1"
    },
    "requestId": "req_2ZK8Q1W9F4M6P7R3"
  }
  ```
</ResponseExample>

## Give this prompt to your agent

<Prompt>
  Use SEC API GET /v1/filings/latest/risk-categories to classify Item 1A risk categories in a selected issuer filing. Preserve `requestId`, `traceparent`, `provenance`, `freshness`, `materialization`, `capability`, `statusNote` 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