REST · one endpoint · three modes

API Reference

Every call is POST https://api.trendsapi.ai/api with your API key in the Authorization header (the Bearer prefix is optional). Set mode in the JSON body. Replace YOUR_API_KEY and you should see a 200 in about a minute.

curl -X POST https://api.trendsapi.ai/api \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"mode":"get_time_series","source":"google search","keyword":"bitcoin"}'

import requests

res = requests.post(
    "https://api.trendsapi.ai/api",
    headers={"Authorization": "Bearer YOUR_API_KEY"},
    json={"mode": "get_time_series", "source": "google search", "keyword": "bitcoin"},
)
print(res.json())

const res = await fetch("https://api.trendsapi.ai/api", {
  method: "POST",
  headers: {
    "Authorization": "Bearer YOUR_API_KEY",
    "Content-Type": "application/json"
  },
  body: JSON.stringify({ mode: "get_time_series", source: "google search", keyword: "bitcoin" })
});
console.log(await res.json());

Only successful requests count against quota. Failed requests are free.

Modes

Pick the operation with mode. Same URL and header every time.

Canonical names match the MCP tools. Aliases: get_trends, trends, time_series and lookup all mean get_time_series; growth means get_growth; top_trends means get_top_trends.

Time series

Weekly history for one source + keyword. Scores are normalized 0-100. About 261 points; the free plan returns the last 12 months.

Request body

Response

{
  "mode":    "get_time_series",
  "source":  "google search",
  "keyword": "bitcoin"
}

[
  {
    "date":    "2026-03-21",
    "value":   47,
    "volume":  25853617,
    "keyword": "bitcoin",
    "source":  "google search"
  }
]

Growth

Point-to-point % change for one keyword. Pass presets or custom date pairs. window defaults to ["12M"]. Comma-separated sources are allowed for comparison.

Request body

Windows

Any number plus a D, W, M or Y suffix, up to 5 years (so 17D or 45D work too), plus MTD, QTD and YTD, plus custom date objects on REST (below). Common examples:

Free plan: growth is clamped to the last 12 months of history.

Custom range

{
  "mode":           "get_growth",
  "source":         "google search",
  "keyword":        "bitcoin",
  "window": ["12M"]
}

{
  "mode":    "get_growth",
  "source":  "amazon",
  "keyword": "nike",
  "window": [
    { "name": "Last Year", "recent": "2025-12-31", "baseline": "2024-12-31" }
  ]
}

{
  "search_term": "nike",
  "data_source": "google search",
  "results": [
    {
      "period":         "12M",
      "growth":         -12.31,
      "direction":      "decrease",
      "recent_date":    "2026-03-21",
      "baseline_date":  "2025-03-22",
      "recent_value":   57,
      "baseline_value": 65
    }
  ]
}

Top trends

Live ranked leaderboard for one feed. No keyword. type is required and must match a feed label exactly. Default limit is 25, max 200.

Request body

{
  "mode":  "get_top_trends",
  "type":  "Google Trends",
  "limit": 10
}

{
  "as_of_ts": "2026-03-26T22:22:25Z",
  "type":     "Google Trends",
  "limit":    10,
  "count":    10,
  "data": [
    [1, "chuck norris"],
    [2, "project hail mary"]
  ]
}

Authentication

Get a free key (100 requests/month, no card). Send it on every request:

Authorization: Bearer YOUR_API_KEY

The Bearer prefix is optional; the bare key works too.

Sources

Keyword sources take source + keyword. Live feeds take type and no keyword. Per-source notes live on /trends.

Keyword sources

Live feeds

What counts as a request

REST: one successful POST is one credit. Boards on MCP: every 10 rows is one request, capped at 10 credits per call. Only successful requests count; failed requests are free. Quotas reset on the first of the month and do not roll over.

Free plan: 100 requests/month. Pricing

Errors

The transport always returns HTTP 200. The real outcome is in the payload: {"statusCode": <int>, "body": <json string>}. Read statusCode, then parse body. Error bodies carry error and message; use message as the operator-facing detail.

{
  "statusCode": 400,
  "body": "{\"error\":\"missing_parameter\",\"message\":\"The 'keyword' parameter is required.\"}"
}

MCP

Same key, same data, from Claude, ChatGPT, Cursor, or VS Code. Endpoint: https://api.trendsapi.ai/mcp.

{
  "mcpServers": {
    "trends-api": {
      "url": "https://api.trendsapi.ai/mcp",
      "headers": { "Authorization": "Bearer YOUR_API_KEY" }
    }
  }
}