Get Events in Trend

Page through the event evidence behind one recent Event Trend bucket.

GET/api/event-trends/{id}/events

Authorizations

Bearer
Authorizationstringheader

Required Bearer API key for programmatic World access.

Example: Bearer nos_sk_...

Parameters

query & path
idstringrequiredpath

Trend result ID returned by Event Trend.

Example: tr_4a45c76c941f482e

bucketdaterequiredquery

Bucket start date returned by Event Trend.

Example: 2026-06-01

groupstringquery

Optional group value to inspect.

Example: negative

limitintegerquery

Page size, up to 200.

Example: 50

cursorstringquery

Opaque next-page cursor.

Example: AAAAAAAAADI

How to use this endpoint

guidance

Use this route immediately after Event Trend to inspect evidence for a bucket or one group. The handle is short-lived; restart the trend request if it expires.

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

Events retained for the selected bucket and optional group.

Example: 91

countinteger

Events returned in this page.

Example: 50

limitinteger

Applied page size.

Example: 50

eventsobject[]

Lite event records with semantic retrieval metadata.

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

next_cursorstring | null

Opaque next-page cursor.

Example: AAAAAAAAADI

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.