Create Event Trend

Aggregate semantic event matches into a compact, dense time series on the server.

POST/api/v2.0-preview/event-trends

Authorizations

Bearer

Authorizationstringheader

Required Bearer API key for programmatic World access.

Example: Bearer nos_sk_...

Body

application/json

querystringrequiredbody

Semantic topic definition.

Example: openai lawsuits

fromdaterequiredbody

Inclusive UTC start date.

Example: 2026-06-01

todaterequiredbody

Exclusive UTC end date.

Example: 2026-09-01

intervalenumbody

day, week, month, or quarter.

Example: month

min_similaritynumberbody

Inclusive exact-cosine threshold; defaults to 0.35.

Example: 0.35

filtersobjectbody

World Search filter DSL.

Example: {}

group_byenumbody

Optional single categorical split such as sentiment or country.

Example: sentiment

How to use this endpoint

guidance

Use Event Trend for a semantic signal over time without downloading the matching events. Buckets are stable under wider date ranges because retrieval uses fixed calendar-quarter partitions. Treat truncated buckets as lower bounds.

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.

idstring

Short-lived handle for Get Events in Trend.

approximateboolean

Always true: semantic retrieval is bounded.

bucketsobject[]

The time series, one bucket per interval in date order.

buckets[].startdate

First day of the bucket.

buckets[].event_countinteger

Matching events in the bucket.

buckets[].coverage_suminteger

Sum of the events' total_coverage.

buckets[].similarity_sumnumber

Sum of the events' similarity to the query.

buckets[].truncatedboolean

True when the bucket's candidate budget filled, so it may hold more matches: treat its counts as lower bounds.

buckets[].groupsobject

The same measures per group_by value; empty without group_by.

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.

401api_key_required — No API key was sent. Send it as Authorization: Bearer <key> or the api-key header.

401invalid_api_key — The API key is invalid or has been revoked.

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.

503api_key_auth_unavailable — API key authentication is temporarily unavailable; retry shortly.

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.