SEC data for legal teams

Use this guide to build a first-pass chronology for issuer, counterparty, or transaction diligence. Keep filing and source identifiers beside each statement. SEC API supports research and retrieval; it does not provide legal advice or replace primary-source review.

Assemble the chronology

Matter task	Route	Required record
Identify the issuer	`GET /v1/entities/resolve`	Resolved name, ticker, CIK, and query used.
Inventory relevant filings	`GET /v1/filings`	Form, filed date, accession number, and filing URL.
Read a known section	`GET /v1/filings/latest/sections/{section_key}`	Filing identity, section key, text availability, and warnings.
Locate sections by terms	`GET /v1/sections/search`	Candidate filing identities before selecting text for review.
Review a documented event record	`GET /v1/events/enforcement` or `GET /v1/events/officer-changes`	Returned record and its source context.

Search results are candidates, not conclusions. Use the returned filing or release identity to read the underlying source before describing it in a memo.

Build one issuer timeline

curl --fail-with-body -sS \
  -H "x-api-key: $SECAPI_API_KEY" \
  "https://api.secapi.ai/v1/entities/resolve?name=Tesla"

curl --fail-with-body -sS \
  -H "x-api-key: $SECAPI_API_KEY" \
  "https://api.secapi.ai/v1/filings?cik=0001318605&forms=8-K,10-K,10-Q,DEF%2014A&limit=25"

curl --fail-with-body -sS \
  -H "x-api-key: $SECAPI_API_KEY" \
  "https://api.secapi.ai/v1/sections/search?q=legal%20proceedings&ticker=TSLA&form=10-K&limit=5"

For a known annual filing section, retrieve the text separately:

curl --fail-with-body -sS \
  -H "x-api-key: $SECAPI_API_KEY" \
  "https://api.secapi.ai/v1/filings/latest/sections/item_3?ticker=TSLA&form=10-K"

Keep the record in bounds

Do not label a result as enforcement history unless the returned SEC record or issuer filing supports that statement. Do not infer liability, materiality, or legal outcome from a search hit. Preserve accession numbers, filing URLs, section keys, dates, requestId, and any warnings with the research file.

Next action

Choose one active diligence question, create a chronology with the inventory and section routes above, then compare it with your current matter-review checklist. Add event routes only where their documented record type and source context meet that checklist.

Filing types and exhibits

Check how form families and exhibits are represented.

Event APIs

Inspect supported event filters and fields.

Freshness and trust

Set source and timing expectations for research output.

Plans & pricing

Products

Workflow guides

Concepts & trust

Tutorials

Migrate to SEC API

Solutions

Compare

API guides by topic

Assemble the chronology

Build one issuer timeline

Keep the record in bounds

Next action

Filing types and exhibits

Event APIs

Freshness and trust

​Assemble the chronology

​Build one issuer timeline

​Keep the record in bounds

​Next action

Filing types and exhibits

Event APIs

Freshness and trust

Assemble the chronology

Build one issuer timeline

Keep the record in bounds

Next action