Event details

Retrieve one event with classifications, entities, coverage, and source evidence.

GET/api/events/{date}/{event_id}

Authorizations

Bearer

Authorizationstringrequiredheader

Required Bearer API key. Programmatic access to the World API needs a key; browsing nosible.world in a browser does not.

Example: Bearer nos_sk_...

Parameters

query & path

datedaterequiredpath

Archive date in YYYY-MM-DD format.

Example: 2026-07-20

event_idstringrequiredpath

Canonical event identifier.

Example: 2026-07-20_en_US_v1_...

How to use this endpoint

guidance

Fetch event detail after discovery. The detail record is the source of truth for a factual claim: it includes the narrative, classifications, entities, coverage counters, and canonical event identity.

Response body

application/json

These are the fields you can build against. Nested names use dot notation; optional sections are called out in their descriptions.

event_idstring

Opaque stable identifier for the event cluster.

Example: 2026-07-20_en_US_v1_...

versionstring

Canonical event-record version.

Example: 1.0

has_tickersboolean

Whether the event has one or more matched securities.

Example: true

event.titlestring

Human-readable event headline.

Example: NVIDIA reports record data center demand

event.descriptionstring

Concise event narrative synthesized from the evidence cluster.

Example: Companies are increasing spending on...

event.datedate

World archive date associated with the event cluster.

Example: 2026-07-20

signalsobject

Normalized signals for sentiment, materiality, and time horizon.

Example: { "sentiment": "positive", "materiality": "high", "time_horizon": "months" }

ontologyobject

Complete populated taxonomy slots, including GICS, IAB, IPTC, and NOSIBLE classifications where available.

Example: { "gics_sector": "Information Technology", "iab_tier_2": "Investing" }

entitiesobject

Named entities detected in the event, grouped by NER type. Each type maps surface forms to mention counts.

Example: { "ORG": { "NVIDIA": 42 } }

coverageobject

Counts describing how broadly the event is covered across documents and unique source domains.

Example: { "total_coverage": 238, "total_netlocs": 61 }

tickersobject[]

Matched security records, including issuer names and alternate identifiers. Empty when has_tickers is false.

Example: [{ "name": "NVIDIA Corp", "ticker_figi": "BBG000BBJQV0", "wiki_qid": "Q182477" }]

provenanceobject[]

Citation-ready supporting evidence with source URL, title, snippets, and event score.

Example: [{ "url": "https://www.reuters.com/...", "title": "...", "snippets": ["..."] }]

timestampsobject

First/last/most-seen timestamps and optional hourly observation counts. Empty when no source carried a timestamp.

Example: { "first_seen": "2026-07-19T16:12:00Z", "last_seen": "2026-07-20T06:55:35Z" }

similarobject

Persisted story-predecessor map of event IDs to cosine similarity. This is distinct from the on-demand /similar route.

Example: { "2026-07-19_en_US_v1_...": 0.83 }

oai_vectorstring

Comma-separated event embedding when the full projection includes it. Treat as model output, not a human-readable field.

Example: 0.0166,-0.0114,...

extraobject

Additional model signals, including per-class sentiment and forward-looking probabilities.

Example: { "signals": { "sentiment": { "prob_positive": 0.81 } } }

coordinateobject|null

Resolved event location, including latitude, longitude, source, and locality when available.

Example: { "lat": 37.33, "lng": -121.89, "source": "geocoded", "city": "Santa Clara" }

signals.sentiment/materialityobject

Structured signal values and scores used to characterize the event.

Example: { "sentiment": "positive", "materiality": "high", "materiality_score": 0.88 }

Responses and errors

HTTP

200Request succeeded. The response body is shown in the panel on the right.

400invalid_request — The date, filter, cursor, identifier, or request combination is invalid.

403access_denied — The requested archive date is outside the caller's World tier.

404not_found — The requested date, entity, ticker, or event does not exist in the accessible index.

410cursor_expired — The cursor was minted against a replaced index build. Restart pagination from the first page.

429rate_limited — The request exceeded the endpoint or account rate limit. Respect Retry-After when supplied.

501backend_not_configured — The World backend is not configured for this deployment.

502backend_error — The BFF could not obtain a valid response from the World backend.

504backend_timeout — The World backend or an upstream data source timed out.