REST API
Trends, creators, clusters, sounds and niches — plus the same work the app does: topics, briefs, text packs, your content plan. JSON, API-key auth, documented in OpenAPI.
Open API docsFor developers
Two ways to reach what powers YoTrends: a REST API for your backend, and an MCP server so an AI assistant can use the data and the features directly.
Trends, creators, clusters, sounds and niches — plus the same work the app does: topics, briefs, text packs, your content plan. JSON, API-key auth, documented in OpenAPI.
Open API docsThe same features as tools for Claude, Cursor and other MCP clients: find trends, track topics, write a brief and a text pack, add an idea to your content plan — without leaving the chat.
How it worksEndpoints return JSON from https://yotrends.ai/api/public/v1. AI work spends your plan's credits, exactly as in the app. The full list, parameters and a live try-it console are in the interactive docs.
| Endpoint | Returns |
|---|---|
GET /me | Your plan, AI credits and remaining calls |
GET /{youtube|tiktok}/trends/videos | Trending videos by market, category and window |
GET /{youtube|tiktok}/trends/influencers | Creators ranked by how often they appear in trends |
GET /{youtube|tiktok}/trends/rising-creators | Channels growing faster than their size |
GET /trends/clusters, /trends/clusters/{id} | Emerging trends and the videos in each |
GET /tiktok/sounds, /tiktok/sounds/{id}/videos | Trending TikTok sounds and the videos using them |
GET /categories, …/{group}/subcategories, …/{group}/trendline | Niches: what is rising, what is cooling, the daily line |
POST /subcategories/{name}/report | AI report on one sub-niche — spends credits |
GET /topics, POST /topics, GET /topics/agenda | Your topics, a new topic, what to film now |
GET /topics/{id}/feed, /topics/{id}/trends, POST /topics/{id}/digest | One topic's videos, trends and AI digest |
POST /trends/clusters/{id}/brief, /topics/{id}/trends/{cluster_id}/brief | Three ready-to-film angles for a trend — spends credits |
POST /topics/{id}/text-pack, /videos/{video_id}/text-pack | A text pack for a topic angle or a video — spends credits |
GET · POST · PATCH · DELETE /content-plan | Your content plan: list, add, change, remove |
GET /channels | Channels you connected |
Every request carries your key in the X-API-Key header. Generate one in Settings once your plan includes API access.
curl -H "X-API-Key: $YOTRENDS_API_KEY" \ "https://yotrends.ai/api/public/v1/youtube/trends/videos?region=US&pageSize=10"
Keys are secret and carry your plan's access. Keep them server-side, never in browser code.
| Plan | REST API calls per month | MCP data calls per month |
|---|---|---|
| Free | Not included | Not included |
| Creator | Not included | 3,000 |
| Pro | Not included | 10,000 |
| Team | 500 | 30,000 |
| Agency | 1,000 | 100,000 |
The MCP server is included with every paid plan; the REST API with Team and Agency. AI work — packs, briefs, reports — spends your plan's credits on either surface and does not count against the MCP allowance. Need a higher allowance? Contact us.