Skip to main content

​
Migrate from sec-api.io

This guide translates common sec-api.io jobs onto SEC API without forcing you to relearn the whole product in one sitting.

​
What changes when you switch

One normalized object model

SEC API keeps provenance, freshness, and materialization visible instead of treating them like optional extras.

Filing types and exhibits map

Check which filing families SEC API retrieves generically, normalizes directly, or only supports inside workflow-specific parsers.

Request diagnostics

Request-Id is first-class across the REST API so support and debugging workflows stay sane.

Shared REST and MCP API

Hosted MCP and REST share the same underlying workflows rather than diverging into two products.

Compact extraction view

Section extraction can return machine-first payloads when you want token efficiency instead of rendered prose.

​
Route mapping

If you depend on arbitrary historical filing URLs or HTML extractor output, keep a temporary fallback path while you finish historical filing-target support. SEC API is stronger on normalized workflows than on raw URL-style extractor parity.
  • /mapping/ticker/{ticker} -> /v1/entities/resolve?ticker={ticker}
  • /mapping/cik/{cik} -> /v1/entities/resolve?cik={cik}
  • / filing search POST body -> /v1/filings query params
  • list of filing types and exhibits -> SEC Filing Types and Exhibits
  • /extractor?url=...&item=1A&type=text -> /v1/filings/latest/sections/item_1a?...&view=compact when latest filing mapping is sufficient
  • /xbrl-to-json -> /v1/statements/{statement_key} or /v1/facts
  • /insider-trading -> /v1/insiders
  • /compensation/{ticker} -> /v1/compensation?ticker={ticker}

​
Request translation examples

​
Ticker mapping

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

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

​
Machine-first section extraction

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

Copy this SEC API prompt for your agent.

​
Migration notes

  • Pin secapi-version in production clients before cutover
  • Keep recording Request-Id during dual-run testing so request diagnostics stay comparable
  • If you depend on arbitrary historical filing URLs for extractor-style requests, keep that path on a temporary fallback until SEC API adds historical filing lookup support
  • If you depend on HTML extractor output, treat that as a current gap and stay on the temporary fallback path
  1. issuer resolution
  2. filing search
  3. statements and facts
  4. section extraction with view=compact
  5. compare and artifact flows once the target plan is enabled

Migrate from Financial Datasets

Compare the second major migration path.

Benchmark workflows

See the current latency, freshness, and workflow proof.

API Reference

Open the exact operation pages once you are ready to wire the calls.