How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

upriver-ai Trends Radar (Beta) API

The Trends Radar (Beta) API from upriver-ai — 7 operation(s) for trends radar (beta).

upriver-ai Trends Radar (Beta) API is one of 12 APIs that upriver-ai publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 6 JSON Schema definitions.

Tagged areas include Trends Radar (Beta). The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 6 JSON Schemas.

This API exposes 7 operations across 7 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.upriver.ai.

7 operations 7 paths 10 schemas 6 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.upriver.ai
Authentication
API Key
Resource Areas
1

Authentication & Security 1

upriver-ai Trends Radar (Beta) API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-API-Key (APIKeyHeader).

Paths & Operations 7

Across 7 paths, the API surfaces 7 operations — 6 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Trends Radar (Beta) 7
GET
/v2/radar
List trends, topics, and breakouts (Beta)
list_radar_beta 12 params → 200422
GET
/v2/radar/breakouts
List product/brand breakouts (Beta)
list_radar_breakouts_beta 11 params → 200422
GET
/v2/radar/facets
List valid filter values (Beta)
get_radar_facets_beta → 200
GET
/v2/radar/items/{item_id}
Get one radar item with live stats (Beta)
get_radar_item_beta 1 param → 200422
POST
/v2/radar/search
Search the radar by natural language (Beta)
search_radar_beta body → 200422
GET
/v2/radar/topics
List durable topics (Beta)
list_radar_topics_beta 11 params → 200422
GET
/v2/radar/trends
List trend moments (Beta)
list_radar_trends_beta 11 params → 200422

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are RadarItem (16 properties), RadarFacetsResponse (7 properties), RadarSearchInput (6 properties), FacetValue (3 properties). Each schema is shown below with its type and property counts.

RadarItemResponse
object
2 properties 1 required
RadarListResponse
object
3 properties 1 required
RadarSearchResult
object
2 properties 2 required
FacetValue
object
3 properties 2 required
RadarSearchInput
object
6 properties 1 required
ValidationError
object
3 properties 3 required
RadarFacetsResponse
object
Legal filter vocabularies — filters are exact-match, so callers need a way to learn valid values instead of guessing.
7 properties 6 required
HTTPValidationError
object
1 property
RadarItem
object
One card: a named slice of cultural activity with its live stats.
16 properties 3 required
RadarSearchResponse
object
2 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

upriver-ai-trends-radar-beta-api-openapi.yml Raw ↑

Other APIs upriver-ai publishes across the network.

upriver-ai Account API
upriver-ai Audience API
upriver-ai Brands API
upriver-ai Breakout Feeds API
upriver-ai Breakout Topics API
upriver-ai Creators API
upriver-ai Images API
upriver-ai Products API
upriver-ai Sponsorships API
upriver-ai Taxonomy API
upriver-ai Trends API
Where this information came from

This is an independent, third-party profile of upriver-ai Trends Radar (Beta) API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.