Skip to main content

GET /v1/filings/latest/risk-categories

Return deterministic Item 1A risk-category coverage for the latest covered filing of an issuer
Audience: application and coding agent.

Canonical metadata

  • requestId
  • traceparent
  • provenance
  • freshness
  • materialization
  • capability
  • statusNote

Example request

curl -X GET \
  -H "x-api-key: $OMNI_DATASTREAM_API_KEY" \
  -H "omni-version: 2026-03-19" \
  "https://api.secapi.ai/v1/filings/latest/risk-categories"

Example response

{
  "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_example_123",
  "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