Intelligence workflows - SEC API for AI

Intelligence routes assemble a defined research job into one response or a queued result. Use them for a target or structured request that needs a company brief, security bundle, portfolio analysis, macro exposure, country report, or filing-footnote investigation with its source context intact.

Start with an issuer bundle

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

Company and security requests require a ticker or CIK. Record returned traces, source references, freshness metadata, warnings, and requestId; an omitted field can reflect available supporting data, not a negative conclusion.

Routes by research job

Method	Path	Job	Output
`GET`	`/v1/intelligence/company`	Company context for a ticker or CIK.	A composed company response.
`GET`	`/v1/intelligence/security`	Security context and catalysts.	A security bundle.
`POST`	`/v1/intelligence/query`	Submit a documented intelligence request.	A completed result or queued job.
`GET`	`/v1/intelligence/query/{jobId}`	Poll a queued request.	Current job state or completed result.
`POST`	`/v1/intelligence/portfolio`	Analyze a documented portfolio body.	Portfolio intelligence output.
`POST`	`/v1/intelligence/watchlist`	Brief a documented watchlist body.	Watchlist output.
`POST`	`/v1/intelligence/country-report`	Build a country research bundle.	Country report output.
`POST`	`/v1/intelligence/macro-exposure`	Calculate portfolio macro sensitivities.	Macro-exposure output.
`POST`	`/v1/intelligence/footnotes/query`	Investigate filing footnotes.	A result or collection.

For POST routes, use the endpoint reference for the exact JSON body. POST /v1/intelligence/query returns 200 for a completed result and 202 for a queued job. Poll the returned job ID to a final state, and handle 202, 404, and 502 as distinct outcomes.

What the response can and cannot prove

An intelligence bundle is a composed research output, not an independent source of record. Coverage and freshness depend on the supporting data planes and supplied body. Follow source references and filing identities for a decision-critical fact, and do not infer an unavailable signal from an omitted field or unfinished job.

Next action

For a completed result, attach its trace and cited sources to the research record. For a queued result, poll the job endpoint and retain its final response rather than treating the acceptance response as analysis.