Use investment intelligence bundles

An intelligence bundle is a route-specific research starting point, not a substitute for source review or an investment conclusion. Use the narrowest bundle that answers the question, then preserve the returned filing, period, provenance, freshness, warning, and trace fields when they are available.

Choose the bundle by the question

Research question	Start with	Follow with
What is currently notable about one security?	`GET /v1/intelligence/security`	Retrieve the cited filing or section before relying on a specific claim.
What company context matters for fundamental review?	`GET /v1/intelligence/company`	Compare the underlying filing period, units, and source records.
What should a reviewer inspect before an earnings event?	`GET /v1/intelligence/earnings-preview`	Separate returned context from a forecast or investment recommendation.
What changed across this watchlist?	`POST /v1/intelligence/watchlist`	Check the identity and evidence for each returned issuer.
What does this submitted portfolio expose?	`POST /v1/intelligence/portfolio`	Keep holdings input, coverage, model context, and residual limitations together.
What do recent filing footnotes say about a defined question?	`POST /v1/intelligence/footnotes/query`	Retrieve the cited filing evidence and report unavailable material clearly.

The Intelligence reference is the authority for accepted inputs and returned fields. Do not assume every bundle contains every filing, factor, market, macro, or coverage representation.

Start with a single-security question

curl --fail-with-body -sS \
  -H "x-api-key: $SECAPI_API_KEY" \
  "https://api.secapi.ai/v1/intelligence/security?ticker=AAPL"

Use the response to identify the next source-backed retrieval. When a conclusion relies on a filing fact, store its accession number and URL, the relevant period, requestId, and route-provided provenance or trace data. Do not present a bundle summary as a direct quote from a filing unless the returned evidence supports that connection.

Ask a bounded footnote question

curl --fail-with-body -sS \
  -X POST \
  -H "content-type: application/json" \
  -H "x-api-key: $SECAPI_API_KEY" \
  -d '{"ticker":"AAPL","query":"What lease obligations are discussed in the latest annual filing?"}' \
  "https://api.secapi.ai/v1/intelligence/footnotes/query"

Phrase the question around a disclosed subject and issuer. If the response reports a limitation, missing source, or partial coverage, carry that state into the review rather than converting it into an absence-of-disclosure conclusion.

Preserve the boundary between evidence and analysis

Record the request parameters, retrieval time, and response identifiers.
Keep returned source links, accession numbers, periods, units, and trace/provenance fields with material claims.
Label model output, inference, and research interpretation separately from reported filing facts.
Retrieve the underlying filing or section when a reader needs to inspect the cited language.
Show stale, unknown, partial, or degraded evidence as a condition, not a silent success.

An intelligence route can reduce the number of calls needed to orient a review. It does not establish completeness, materiality, legal advice, or a forecast.

Intelligence reference

Inspect route contracts before adding a bundle to production.

Filing search

Find the source filing behind a research path.

Freshness and source evidence

Set a decision policy for returned research evidence.

Plans & pricing

Products

Workflow guides

Concepts & trust

Tutorials

Migrate to SEC API

Solutions

Compare

API guides by topic

Use investment intelligence bundles

Choose the bundle by the question

Start with a single-security question

Ask a bounded footnote question

Preserve the boundary between evidence and analysis

Read next

Intelligence reference

Filing search

Freshness and source evidence

​Choose the bundle by the question

​Start with a single-security question

​Ask a bounded footnote question

​Preserve the boundary between evidence and analysis

​Read next

Intelligence reference

Filing search

Freshness and source evidence

Choose the bundle by the question

Start with a single-security question

Ask a bounded footnote question

Preserve the boundary between evidence and analysis

Read next