Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.secapi.ai/llms.txt

Use this file to discover all available pages before exploring further.

​
Migrate from financialdatasets.ai

This guide helps you swap financialdatasets.ai workflows onto Datastream without losing the normalized statement views you already depend on.

​
What changes when you switch

Primary-source lineage

Datastream exposes SEC-backed provenance and freshness alongside normalized rows.

More than statements

Filings, sections, ownership, compensation, webhooks, streams, and MCP all live in the same product.

Usage signals in every response

Meter and plan headers stay visible while you migrate and benchmark.

Better section and filing context

Datastream gives you normalized financials plus the filing context that produced them.

​
Route mapping

  • /financials/income-statement -> /v1/statements/income_statement
  • /financials/balance-sheet -> /v1/statements/balance_sheet
  • /financials/cash-flow-statement -> /v1/statements/cash_flow_statement
  • /financial-metrics -> /v1/facts plus statement endpoints
  • /sec-filings -> /v1/filings and /v1/filings/latest
  • /insider-trades -> /v1/insiders

​
Request translation examples

​
Income statement

curl -H "x-api-key: $OMNI_DATASTREAM_API_KEY" \
  "https://api.secapi.ai/v1/statements/income_statement?ticker=AAPL&period=annual&limit=4"

​
Balance sheet

curl -H "x-api-key: $OMNI_DATASTREAM_API_KEY" \
  "https://api.secapi.ai/v1/statements/balance_sheet?ticker=AAPL&period=annual&limit=4"

​
Filing retrieval

curl -H "x-api-key: $OMNI_DATASTREAM_API_KEY" \
  "https://api.secapi.ai/v1/filings/latest?ticker=AAPL&form=10-K"

​
Migration notes

  • Pin omni-version and compare statement-level fields before swapping production dashboards
  • Use /v1/facts when you need tag-level primary-source values instead of a pre-aggregated metrics bundle
  • Expect larger payloads than financialdatasets.ai on some statement calls because Omni includes provenance and richer structure
  • If you only need a token-efficient machine summary, prefer compact section mode and the statement-specific endpoints instead of full rendered filings
  1. statements
  2. facts
  3. filing search and latest filing retrieval
  4. insider and compensation workflows
  5. MCP or artifact workflows if you are consolidating tool surfaces

Statements reference

Open the exact normalized statement and bundle endpoints.

Ownership workflows

See the institutional and beneficial ownership flows that sit beyond standard financials APIs.

Auth and pricing

Understand plan headers, usage posture, and onboarding before cutover.