Developer portal · Pro integration

Build with source-backed customer-interest evidence.

What’s Trending exposes a versioned REST API and Streamable HTTP MCP server for an authenticated Pro workspace. Reads return the workspace’s configured market, ranked trends, and original public evidence. Scan calls collect and persist new evidence.

Quickstart

Sign in and complete a workspace.
Activate Pro.
Open Settings → Agent access and create a workspace-scoped key.
Start with a read request and keep the key server-side.

curl "https://api.whatstrending.cc/v1/trends?days=30" \
  -H "Authorization: Bearer wt_live_YOUR_KEY"

Use the OpenAPI 3.1 contract for complete request and response schemas, or read the API guide.

API keys and environments

Keys are created and revoked self-serve in the signed-in application. Each key belongs to one workspace, is displayed once, and is stored only as a hash. What’s Trending currently provides one production API at https://api.whatstrending.cc; it does not advertise a separate public sandbox. Test integrations with read-only endpoints before calling a scan.

REST endpoints

Method	Path	Purpose
GET	`/v1/workspace`	Read the configured market, WordBank, and competitor watchlist.
GET	`/v1/trends`	Read ranked topics for a supported lookback window.
GET	`/v1/evidence`	Read public source URLs, excerpts, timestamps, and available engagement.
POST	`/v1/scans`	Collect and persist a fresh scan, subject to the workspace interval.

Retry a scan safely

Send a unique Idempotency-Key when starting a scan. A completed retry with the same workspace and key replays the original response instead of collecting twice. Keys accept 8–128 ASCII letters, digits, dots, underscores, colons, or hyphens and are retained for 24 hours.

curl -X POST "https://api.whatstrending.cc/v1/scans" \
  -H "Authorization: Bearer wt_live_YOUR_KEY" \
  -H "Idempotency-Key: campaign-refresh-2026-08-26"

MCP tools

The Streamable HTTP endpoint at https://api.whatstrending.cc/mcp exposes get_trends, list_evidence, and run_scan. Tool discovery is public; tool calls use the same Bearer key. Read the MCP server card.

Plans, limits, and safety

REST and MCP access require Pro. Agent-triggered scans are limited to once per hour per workspace. Source coverage and engagement fields vary by platform; missing metrics mean unavailable, not zero. Preserve original source URLs and confirm user intent before starting a scan.

Pricing · Authentication · Agent integration guide · Contact