World API/GET EVENTS

By day

List the events in a dated World archive slice with sorting and pagination.

GET/api/events/{date}

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

limitintegerquery

Page size.

Example: 100

sort_byenumquery

total_coverage, total_netlocs, or event_id.

Example: total_coverage

descbooleanquery

Sort descending when true.

Example: true

offsetintegerquery

Number of events to skip.

Example: 0

Related in NOSIBLE World

World · Map ↗Open this result set on the event map, filtered to the same windowWorld · Trend ↗Plot the same query as a historical event signalWorld · Chaos ↗Watch the unfiltered crawl the ontology is built from

How to use this endpoint

guidance

Use Events for a date-scoped snapshot when you want deterministic ordering and pagination rather than relevance ranking.

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.

totalinteger

Total events available for the date before pagination.

Example: 7418

countinteger

Number of events in this page.

Example: 100

limitinteger

Applied page size.

Example: 100

offsetinteger

Applied offset.

Example: 0

sort_bystring

Effective ordering key. Supported aliases include total_coverage, total_netlocs/n_sources, event_id, and materiality_then_coverage.

Example: materiality_then_coverage

descboolean

Whether the applied sort is descending.

Example: true

eventsobject[]

Lite event records for the date. Fetch event detail for the complete record.

Example: [{ event_id, event, signals, coverage }]

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.