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.

​
API Overview

The API is built for real investor work. It keeps the contract compact, the source trail visible, partial-state behavior explicit, and the surface consistent across REST, SDKs, CLI, and hosted MCP.

​
Authentication

API keys are the primary authentication method for all plans. Use the x-api-key header on every REST request; the same credential works across SDK and CLI clients. See Auth, Billing, and First Utility for the full model. OAuth/SSO via WorkOS is planned for the enterprise tier in 2026 Q3+; hosted MCP clients use WorkOS OAuth discovery today and that surface is unchanged.

​
What the API is optimized for

Investor workflows

The API is optimized for repeated issuer, filing, section, statements, ownership, governance, fund, and signal workflows.

Compact payloads

The payloads stay useful for applications and agents without turning into raw filing dumps.

Visible provenance

Provenance, freshness, and trace references stay explicit instead of being pushed into side channels.

Stable interfaces

REST, SDKs, CLI, and hosted MCP follow the same contract model.

​
Core design rules

1

Version requests

Use Omni-Version so production behavior does not shift underneath you.
2

Correlate requests

Keep Request-Id in logs and downstream artifacts.
3

Use cursor pagination

List endpoints paginate with cursors instead of offset math.
4

Keep metadata with the payload

Provenance, freshness, materialization, and trace references belong with the data.
5

Prefer structured contracts

Datastream favors useful structured workflows over raw passthroughs.
6

Respect explicit partial states

Treat values like supported, degraded, unavailable, and rights-scoped coverage flags as part of the contract, not edge-case trivia.

​
What makes the contract different

  • provenance: where the data came from
  • freshness: how current the data is
  • materialization: how the current output was produced
  • trace: how to get from a filing-derived value back to the source filing and page when available
These fields matter because investor agents need more than a value. They need the trail behind the value.

​
Event delivery rules

  • webhook delivery uses signed POST requests with x-omni-signature
  • delivery headers include x-omni-event-id, x-omni-event-type, and x-request-id
  • current event families include artifacts, webhooks, and stream subscriptions
Datastream is not trying to be a generic raw filing tunnel. It is designed around the workflows serious investors and investor agents actually repeat.

API conventions

Read the wire-level defaults and shared rules.

API Reference

Jump to the exact call you need.

Freshness and trust

See how the source trail and freshness posture stay visible.