Node.js Trends API integration with fetch

A Node.js Trends API client is a Bearer-authenticated POST to https://api.trendsapi.ai/api, then a second JSON.parse on the body string. On 2026-08-09, Google Search interest for Node.js sat at 42.0 on 2026-08-08 with 30D growth of -35.38%, 3M of -49.4%, 6M of 16.67%, and 12M of 90.91%. The same pull on the npm source showed react at score 100.0 with 162,776,333 weekly downloads on 2026-08-08 and 12M volume growth of 289.26%. That pairing is the point of the integration: search interest and package volume share one JSON contract.

Minimal fetch client

Node 18+ ships fetch. Set TRENDSAPI_API_KEY and keep the double parse in one helper. Free tier allows 100 successful requests per month. Only HTTP 200 responses count against quota. Starter is 5,000, Pro is 25,000, Business is 100,000.

const API_URL = "https://api.trendsapi.ai/api";
const API_KEY = process.env.TRENDSAPI_API_KEY;

async function trendsApi(payload) {
  const res = await fetch(API_URL, {
    method: "POST",
    headers: {
      Authorization: `Bearer ${API_KEY}`,
      "Content-Type": "application/json",
    },
    body: JSON.stringify(payload),
  });
  if (!res.ok) {
    throw new Error(`HTTP ${res.status}`);
  }
  const envelope = await res.json();
  // body is a JSON string; parse it a second time
  return JSON.parse(envelope.body);
}

const growth = await trendsApi({
  mode: "get_growth",
  source: "google search",
  keyword: "Node.js",
  percent_growth: ["30D", "3M", "6M", "12M"],
});
console.log(growth.results[0].growth);

The first mistake most clients make is reading envelope.body.results. That fails because body is still a string after res.json().

Google Search growth for Node ecosystem terms

Pulled on 2026-08-09 with source set to google search. Recent points land on 2026-08-08.

Node.js is up 90.91% over 12M while short windows are down. Next.js sits at 13.0 with a 30D drop of -75.93%. Keep both windows in the payload; they answer different questions.

For source docs and field notes, see Google Search trends. For a Python twin of this client pattern, see the Python Trends API guide.

npm volumes on the npm source

Keywords on source: "npm" must be exact package names as listed on the registry. Pulled on 2026-08-09 with custom dates ending on 2026-08-08 so the comparison skips a sparse tip week that returned score 0.0 and volume 0 on 2026-08-15 for preset windows.

react hit the local max score of 100.0 on 2026-08-08. next trailed at 95.2 with faster 30D score growth (17.1% vs 6.16%). express still shows 180.99% score growth over ~12M ending 2026-07-25.

Custom date objects in percent_growth look like this:

const npmGrowth = await trendsApi({
  mode: "get_growth",
  source: "npm",
  keyword: "react",
  percent_growth: [
    { name: "30d_to_aug8", recent: "2026-08-08", baseline: "2026-07-11" },
    { name: "12m_to_aug8", recent: "2026-08-08", baseline: "2025-08-09" },
  ],
});

Field notes for package downloads live on the npm trends page. For a product-demand walkthrough that uses the same Node helper against Amazon and Google Shopping, see soccer cleats multi-source signals in Node.

get_time_series for charts and alerts

When a dashboard needs every weekly point, switch mode to get_time_series. The react series returned 261 points on 2026-08-09. Recent complete weeks included 2026-08-01 at score 99.7 with volume 162,348,333 and 2026-08-08 at score 100.0 with volume 162,776,333. The next stub week 2026-08-15 returned 0.0 / 0; treat that tip as incomplete until volume is non-zero.

const series = await trendsApi({
  mode: "get_time_series",
  source: "npm",
  keyword: "react",
});
const complete = series.filter((row) => row.volume > 0);
const last = complete[complete.length - 1];
console.log(last.date, last.value, last.volume);

Use get_top_trends only for live boards with no keyword. On 2026-08-09 the Google Trends board listed perez hilton at rank 1 and spokane fires at rank 2 as of 2026-08-09T10:01:34Z.

Error handling and quotas

Check HTTP status before parsing. Then check statusCode on the envelope. Growth rows can return per-period status: "error" with codes such as collapsed_range or date_out_of_range while other periods still succeed. Log the period and keep the successful rows.

Quota reminder: only successful 200 responses count. A failed auth call does not burn the free 100. Cache responses for cron jobs that poll the same keyword every hour.

When to use this over scrapers

A Node scraper against unofficial Google Trends endpoints breaks when cookies or consent walls change. Trends API keeps one endpoint, Bearer auth, and a 0-100 score across Google Search, npm, Amazon, TikTok, and the rest of the documented source list. For broader alternative framing, see the Google Trends API alternative page.