Resolve, then fetch - SEC API for AI

Resolve an issuer before you fetch filings, facts, statements, or a named intel job. GET /v1/entities/resolve is the identity call. The stores and the packer take that identity; they do not invent it.

curl --fail-with-body -sS \
  -H "x-api-key: $SECAPI_API_KEY" \
  -H "secapi-version: 2026-03-19" \
  "https://api.secapi.ai/v1/entities/resolve?ticker=AAPL&view=agent"

Keep id, cik, ticker, matchConfidence, and matchBasis when they are returned. A low-confidence match is a correction task, not a join key. Do not infer a CIK from a ticker string or an old filing URL.

The path

Resolve the issuer, manager, or security.
Carry the returned CIK (and entity id when present).
Fetch one store, or run one named intel job.

After resolve	Fetch	First route
The official record	Filings store	`GET /v1/filings/latest`
One disclosed number	Facts	`GET /v1/facts`
A financials page	Statements	`GET /v1/statements`
Why a price moved	Factors	`GET /v1/factors/catalog`
A country print	Macro indicators	`GET /v1/macro/indicators`
A cited assembly	Intel packer	Named intel jobs

Letters and authenticated situations are gated stores. They 404 when that store is dark. Do not make them the first curl.

curl --fail-with-body -sS \
  -H "x-api-key: $SECAPI_API_KEY" \
  -H "secapi-version: 2026-03-19" \
  "https://api.secapi.ai/v1/filings/latest?ticker=AAPL&form=10-K&view=agent"

The second request returns the current latest matching filing. Keep the accession number, form, filing date, filing URL, and requestId when present.

What resolve is not

Job	Route	Use it when
Identity	`GET /v1/entities/resolve`	You have a ticker, CIK, FIGI, name, or other identifier and need one entity.
Canonical search	`GET /v1/entities`	You need a paginated list of canonical entities.
EDGAR catalog search	`GET /v1/entities/edgar`	You need paginated EDGAR source records. Not an identity peer of resolve.

An empty resolve request is invalid. Company overview (GET /v1/companies/overview) is a company view, not a substitute for resolve and not the intelligence product.

Next

Object graph — the objects you fetch after resolve
Response views and include — view=agent and include=
Named intel jobs — packs and reports
First request flows — REST, SDK, CLI, and MCP