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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
upriver-ai

upriver-ai Trends API

The Trends API from upriver-ai — 6 operation(s) for trends.

Documentation Provider Profile APIs.io OpenAPI GitHub

upriver-ai Trends 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. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 6 JSON Schemas.

This API exposes 6 operations across 6 paths, and defines 18 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.

6 operations 6 paths 18 schemas 5 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 API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-API-Key (APIKeyHeader).

Paths & Operations 6

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

Trends 6
POST
/v2/trends/broad
Trends List
trends_broad_v2 1 param body → 200422
GET
/v2/trends/{trend_id}
Trend Details
get_trend_by_id_v2 1 param → 200422
GET
/v2/trends/{trend_id}/media
Media Samples
trends_media_v2 3 params → 200422
GET
/v2/trends/{trend_id}/playback
Audio Playback
trends_playback_v2 2 params → 200422
GET
/v2/trends/{trend_id}/similar
Similar Trends
trends_similar_v2 2 params → 200422
GET
/v2/trends/{trend_id}/traction
Traction Graph
get_trend_traction_v2 2 params → 200422

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are TrendDetailResponse (44 properties), TrendsBroadInput (33 properties), BroadTrend (17 properties), ResponseMeta (6 properties). Each schema is shown below with its type and property counts.

TrendsBroadInput
object
Payload model for the /trends/broad endpoint.
33 properties
TrendTag
object
A tag attached to a trend (e.g., 'Beauty', 'Comedy').
4 properties 1 required
TrendDetailResponse
object
Response for GET /trends/{id}. Only includes fields returned by the endpoint.
44 properties 3 required
ScopeConfig
object
Where/when to look for signals and which platforms to use. These are query filters (not brand metadata). Time window: - Use 'fromtime' (start) and 'totime' (en…
3 properties
ResponseMeta
object
Response-level metadata (flat and endpoint-agnostic). Provenance (always present): - generatedat, timewindow, industries Diagnostics (gated by metadatamode): -…
6 properties 1 required
BroadTrend
object
A single broad cultural trend with social relevance.
17 properties 2 required
AppliedFilter
object
Structured record of a filter or normalization that affected the returned payload. Good for audit/debug; suitable for 'metadatamode=debug'.
3 properties 2 required
ValidationError
object
3 properties 3 required
SimilarTrendsResponse
object
Response for GET /v2/trends/{id}/similar.
2 properties 2 required
TrendsBroadResponseConfig
object
How to format the response.
5 properties
TrendsBroadTargetAudience
object
Where to look for trends.
1 property
HTTPValidationError
object
1 property
TrendsBroadResponse
object
Broad cultural trend detection results. Identifies current, socially relevant cultural topics that could inspire ad creative.
4 properties 2 required
DebugInfo
object
Optional development diagnostics (included when metadatamode='debug'). Times and counts should refer to the current request execution only.
3 properties 2 required
SourceFilters
object
4 properties
TrendMatchResult
object
A single matched trend with similarity score.
3 properties 3 required
ContentScopeCounts
object
Count of returned items by ContentScope. These counts reflect the final payload after confidence/limit filters.
3 properties
ResponseCounts
object
Top-level count diagnostics for the response payload. - 'total' MUST equal the number of items returned in this endpoint's main list. - 'byscope' breaks down t…
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs upriver-ai publishes across the network.

upriver-ai Account API
AE Profile APIs.io
upriver-ai Audience API
AE Profile APIs.io
upriver-ai Brands API
AE Profile APIs.io
upriver-ai Breakout Feeds API
AE Profile APIs.io
upriver-ai Breakout Topics API
AE Profile APIs.io
upriver-ai Creators API
AE Profile APIs.io
upriver-ai Images API
AE Profile APIs.io
upriver-ai Products API
AE Profile APIs.io
upriver-ai Sponsorships API
AE Profile APIs.io
upriver-ai Taxonomy API
AE Profile APIs.io
upriver-ai Trends Radar (Beta) API
AE Profile APIs.io
#Trends
← Back to U APIs
API Details
ID
upriver-ai:upriver-ai-trends-api
Base URL
https://api.upriver.ai
Docs
https://docs.upriver.ai/api-reference/
Provider
upriver-ai
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=upriver-ai-trends-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/upriver-ai-trends-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of upriver-ai Trends 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.