# Google Trending Searches

> What people search now, per country: Google Trends trending searches as JSON

- Vendor: `googletrendingnow` · version 1.0 · category Analytics · tags google trends, trending searches, search trends, news monitoring, content planning
- Datasource: custom HTTP routes
- Marketplace page: https://apiclay.com/api/googletrendingnow
- This document: https://apiclay.com/docs/googletrendingnow.md
- OpenAPI 3.1: https://apiclay.com/api/googletrendingnow/openapi.json
- MCP: connect https://api.apiclay.com/v1/mcp (see https://apiclay.com/llms.txt), then `apiclay_describe_api` with vendor `googletrendingnow`
- Updated: 2026-11-18

## About

## Google Trending Searches

The searches trending right now in a country, from Google Trends 'Trending now', as clean JSON.

### Route

#### /trending

Trends for a country: trend, search_volume (e.g. 200K+), increase (e.g. 1,000%), started (e.g. 3 hours ago), status (Active or how long it lasted) and related searches. 25 per call. Rendered in a browser (adds the platform browser fee).

```bash
curl -G 'https://api.apiclay.com/v1/api/googletrendingnow/trending' -H 'token: YOUR_TOKEN' --data-urlencode 'geo=US' --data-urlencode 'hours=24'
```

### Notes

geo is a two-letter country code (US, IN, GB, DE ...). hours is the time window: 4, 24, 48 or 168. Data comes from the public Google Trends page. Not affiliated with Google.

## Pricing

- Pay as you go: 0.01 credits/request
- Trial: 10 free requests per buyer
- Billing order: trial requests -> subscribed plan requests -> pay as you go. 1 credit's USD value is shown on the marketplace page.
- Browser rendering (0.005 credits per rendered call): A call that renders the page in a browser adds the browser fee to the route price: routes with render mode js, routes with render mode auto when the call switches to the browser (pre-charged, refunded when it does not), and calls sent with `X-ApiClay-Render: js`.
- Trial and plan requests still pay the browser fee.
- Response headers on a billed call: `X-ApiClay-Browser-Fee`.

## HTTP routes

Only the public, buyer-facing parts of each route are listed; vendor-side credentials stay on the gateway.

### GET /trending — Trending now
- Gateway: `GET https://api.apiclay.com/v1/api/googletrendingnow/trending`
- Public query params: `geo` (string, required), `hours` (string)
- Upstream proxy: ApiClay proxy paid by the vendor (data cap 5.8 MB per call). Fetched through an ApiClay proxy paid by the vendor; a response larger than the route's data cap fails with 502 and is refunded in full.

## Call example

```bash
curl -X GET "https://api.apiclay.com/v1/api/googletrendingnow/trending?geo=<geo>" \
  -H "token: <YOUR_APICLAY_TOKEN>"
```

Index of every published API: https://apiclay.com/llms.txt
