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 Taxonomy API

The Taxonomy API from upriver-ai — 2 operation(s) for taxonomy.

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

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

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

Paths & Operations 2

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

Taxonomy 2
POST
/v1/categories/search
Media Categories Search
search_categories body → 200422
GET
/v1/media_categories
Media Categories
media_categories → 200

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are CategoryMatch (6 properties), TaxonomyCategory (6 properties), ValidationError (3 properties), CategoriesResponse (2 properties). Each schema is shown below with its type and property counts.

CategorySearchInput
object
Input for category search endpoint.
2 properties 1 required
TaxonomyCategory
object
A single taxonomy category item (L1 or L2).
6 properties 3 required
CategorySearchResponse
object
Response from category search endpoint.
2 properties 2 required
CategoryMatch
object
A matched category with confidence score. Note: When passing the matched category to other endpoints that use embedding-based resolution (like /sponsors), use…
6 properties 4 required
ValidationError
object
3 properties 3 required
HTTPValidationError
object
1 property
CategoriesResponse
object
Response containing lists of L1 and L2 taxonomy categories.
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

upriver-ai-taxonomy-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 Trends API
upriver-ai Trends Radar (Beta) API
Where this information came from

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