Skip to main content
Trends Radar groups cultural activity into three item types: participatory trend moments, durable topics, and breakouts for products or brands gaining attention. Use the /v2/radar endpoints to browse them, inspect one item, or search with a natural-language query.
Trends Radar is in beta. Response shapes may change, and this surface may converge with /v2/trends. Every successful response includes a beta note.

​
Before you start

You need an Upriver API key. Send it in the X-API-Key header on every request. The examples below use https://api.upriver.ai and an environment variable named UPRIVER_API_KEY.

​
Browse radar items

Start with the combined list. It defaults to the general_market catalog, orders by rising, and returns up to 25 items. Use limit and offset to page through results; total counts all items matching your filters.
A successful response has this shape:
The response above is illustrative. Optional fields, including stats, may be null, and the contents of stats vary by item. For one type at a time, use these list endpoints. They accept the same list filters as /v2/radar, except card_type:

​
Choose filters and sort order

Call GET /v2/radar/facets to discover valid values for lifecycle, persona, and brand_safety. These filters use exact values. The combined list also accepts card_type; all list endpoints accept entity, platform, min_size, since, sort, limit, and offset. since is an ISO 8601 timestamp and keeps items refreshed at or after that time.
The available list sort values are rising, newest, value, freshness, and size. The legacy momentum value is also accepted and uses the same ordering as rising. Use an item’s id with GET /v2/radar/items/{item_id} to fetch it with live stats and a stats.traction history. To find relevant items by description, send a query of 2 to 500 characters to POST /v2/radar/search:
Search returns results, each containing an item and match_score. You can also filter search by card_type, program, lifecycle, and brand_safety.

​
If a request fails

  • 401: Check that X-API-Key contains an active key.
  • 404 on item detail: The item ID is unavailable.
  • 422: Check parameter types and limits. For example, list limit is 1–100 and search limit is 1–50.
  • 429: Your key has reached its Radar request quota. Limits depend on your plan; contact Upriver support if you need more capacity.
  • 503 on search: Search is temporarily unavailable; retry later.