Topic Trend

Turn a keyword or phrase into a time series showing its prevalence across the web.

POST/search/v2/topic-trend

Related NOSIBLE resources

research & data

Inspect the Search data dictionary or read NOSIBLE research for implementation context and methods.

Authorizations

apiKey

Api-Keystringrequiredheader

Your NOSIBLE API key from the API Dashboard.

Example: nos_sk_...

Body

application/json

querystringbody

The topic to measure over time. Defaults to the service example; when supplied, use at least five characters and keep the phrase stable when comparing dates.

Example: artificial intelligence

sql_filterstringbody

Optional SQL filter over the trend index.

Example: SELECT loc, published FROM engine

How to use this endpoint

guidance

Use Topic Trend to turn a phrase into a historical prevalence series. Keep the query stable when comparing time periods, and use sql_filter only when you need a reproducible document-level constraint. The response is a date-keyed object, so preserve the keys when joining it to a market calendar.

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.

queryobject

Effective trend query and filter parameters.

Example: { "query": "AI chips", "sql_filter": "SELECT loc, published FROM engine" }

query.querystring

The phrase measured by the trend engine.

Example: AI chips

responseobject

Date-keyed prevalence scores. Each key is an ISO date and each value is the observed score for that day.

Example: { "2026-07-20": 0.42 }

response.2026-07-20number

Example score for one date in the response map. Scores are comparable within the same query and request configuration.

Example: 0.42

Responses and errors

HTTP

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

400invalid_request — The request is syntactically valid JSON but a value, date, filter, or combination of fields is invalid.

401unauthorized — The required API key or Bearer credential is missing or invalid.

422validation_error — The request shape is understood but one or more values fail validation.

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

502upstream_error — An upstream retrieval service failed while processing the request.

504upstream_timeout — An upstream retrieval service did not respond within the request timeout.