GET /v1/filings/{accession_number}/sections/{section_key}

curl -X GET -H "x-api-key: $SECAPI_API_KEY" -H "secapi-version: 2026-03-19" "https://api.secapi.ai/v1/filings/0000000000-26-000001/sections/item_7?view=agent"

{
  "object": "section",
  "ticker": "EXAMPLE",
  "accessionNumber": "0000000000-26-000001",
  "key": "item_7",
  "startOffset": 2400,
  "endOffset": 3120,
  "snippet": "Illustrative Item 7 management-discussion snippet.",
  "accession": "0000000000-26-000001",
  "section_key": "item_7",
  "char_start": 0,
  "char_end": 50,
  "highlighted_snippet": "Illustrative **Item 7** management-discussion snippet.",
  "source_url": "https://www.sec.gov/Archives/edgar/data/0000000/000000000026000001/example-2025-10k.htm",
  "requestId": "req_2ZK8Q1W9F4M6P7R3"
}

Extract a named section from one accession-number filing.

Audience: engineers and agents that need reproducible section extraction from one immutable filing.

Coverage and source scope

Retrieve a supported canonical section from one explicitly selected SEC filing. The accession number fixes the source document; preserve it with the returned source URL and section key for a reproducible citation. A missing section or unresolved accession does not establish that the underlying disclosure is absent.

Canonical metadata

object
ticker
accessionNumber
key
snippet
accession
section_key
source_url
requestId

Example request

curl -X GET -H "x-api-key: $SECAPI_API_KEY" -H "secapi-version: 2026-03-19" "https://api.secapi.ai/v1/filings/0000000000-26-000001/sections/item_7?view=agent"

Example response

{
  "object": "section",
  "ticker": "EXAMPLE",
  "accessionNumber": "0000000000-26-000001",
  "key": "item_7",
  "startOffset": 2400,
  "endOffset": 3120,
  "snippet": "Illustrative Item 7 management-discussion snippet.",
  "accession": "0000000000-26-000001",
  "section_key": "item_7",
  "char_start": 0,
  "char_end": 50,
  "highlighted_snippet": "Illustrative **Item 7** management-discussion snippet.",
  "source_url": "https://www.sec.gov/Archives/edgar/data/0000000/000000000026000001/example-2025-10k.htm",
  "requestId": "req_2ZK8Q1W9F4M6P7R3"
}

Reproducible filing coverage

Use this route after saving an accession number from a filing result. The accession number fixes the filing selection; optional ticker, CIK, and form are hints rather than a replacement for it. submission_file_limit bounds older-coverage resolution. Preserve provenance with the excerpt so a reader can return to the source filing.

Errors

Invalid response mode or unsupported request values return a contract-aware 400. 404 section_lookup_failed means the requested accession or section could not be resolved; it is not evidence that the section contains no relevant text.

Give this prompt to your agent

Failure posture

keep the accessionNumber and section_key as the citation identity
preserve source_url and requestId
verify the accession and section key before widening a lookup
do not silently fall back to a different filing when the requested accession fails

GET /v1/filings/{accession_number}/export GET /v1/filings/latest

​Coverage and source scope

​Canonical metadata

​Example request

​Example response

​Reproducible filing coverage

​Errors

​Give this prompt to your agent

​Failure posture

Coverage and source scope

Canonical metadata

Example request

Example response

Reproducible filing coverage

Errors

Give this prompt to your agent

Failure posture