Market events API

Build stock and crypto workflows on revisioned market events

DataCedar turns source documents into a durable event spine so applications can search what happened now and reproduce what was available then.

Built for: Developers building event feeds, research agents, backtest annotations, SSE consumers, or signed alert pipelines.

Get a free API key Read the event API docs

Build a stable event feed

Use durable IDs and immutable revisions instead of treating an edited headline as the same unversioned record.

Annotate point-in-time research

Store effective, published, and known-at clocks with the evidence eligible at the simulated cutoff.

Deliver events safely

Use REST, resumable SSE, signed webhooks, or MCP under the same account, latency, history, and source-rights rules.

Live product proof · checked 23 July 2026 UTC

Stable identity and revision are present in the response.

A live BTC event query returned separate event and revision IDs together with effective and known-at clocks, confirmation state, evidence counts, licensing state, and record-level latency. That is the contract required to process corrections without overwriting history.

2 IDs
Stable event plus immutable revision
2 clocks
Effective-at and known-at remain separate
1 document
Evidence count on the checked event
Run the keyless MCP demo Inspect live coverage
Verified response excerpt
{
  "event_id": "256dc527dbc2127721ce1a1a9d02ba83",
  "revision_id": "572f93fce1d0fb1c6374b0f79daefe58",
  "effective_start_ms": 1784712707000,
  "known_at_ms": 1784712887770,
  "license_state": "official_project_metadata",
  "status": "confirmed"
}
  • The excerpt was returned by datacedar_search_events through the live keyless MCP demo.
  • The response also reported availability: realtime and latency_seconds: 0 for this record only.
  • REST, SSE, webhooks, and MCP apply account, history, latency, and source-rights rules at serving time.
Working surface

Retrieve a stable event and its revisions.

Build against stable event IDs, evidence citations, resolved entities, effective and known-at times, corrections, clusters, coverage, SSE, webhooks, and MCP.

GET /v3/intelligence/events/{event_id}
curl 'https://api.datacedar.com/v3/intelligence/events/{event_id}' \
  -H 'Authorization: Bearer dc_...'
Response model

Event fields that survive corrections and reruns.

event_id + revision

The identity survives correction while every material version remains separately addressable.

effective_at

When the underlying market or company event took effect, independent of discovery time.

published_at + known_at

When the evidence was published and when it became eligible in DataCedar stay distinct.

entities[] + confidence

Resolved assets and organizations retain relationship type, match evidence, and review confidence.

evidence[]

Primary and supporting documents identify their source, rights version, and role in the event.

cluster_id + correction_state

Related reports, conflicts, replacements, and tombstones can be reconciled without deleting history.

Workflow

From source acquisition to a delivery-safe event record.

01

Acquire

Rights-approved connectors preserve raw source objects, retrieval time, checksums, and source identifiers.

02

Normalize

Deterministic rules map documents into an event taxonomy and resolve entities with reviewable confidence.

03

Revise

New evidence creates an event revision or related cluster record rather than overwriting historical truth.

04

Distribute

REST, SSE, webhooks, and MCP apply the same plan latency, rights, history, and account filters.

Built for

Event-driven research and backtest annotations.
Cited agent retrieval through REST or MCP.
Resumable SSE feeds and HMAC-signed webhook delivery.

Explicit boundaries

Generated fields retain their evidence set and cutoff.
Low-confidence matches enter review rather than silently becoming facts.
Rights revocation is checked at serving and delivery time.

Frequently asked questions

What counts as a market event?

The taxonomy includes company, SEC, earnings, macro, regulatory, exchange, listing, protocol, governance, incident, security, and correction events. Each class retains its own entities, clocks, evidence, and coverage state.

How are corrections represented?

The stable event ID links immutable revisions. Clients can inspect the current revision, retrieve a historical cutoff, and process correction or tombstone delivery without losing the earlier record.

Do REST, webhooks, and MCP return different rights states?

No. They compose the same serving rules. Account plan, history window, latency class, source rights, removal state, and display policy are enforced before each delivery channel returns the event.

Build your first cited event query free.

Create a key, retrieve an event, and verify its evidence, entity matches, clocks, corrections, and coverage state before integrating.

Get a free API keyRead the event API docs