Bright Data's Google Trends path is a SERP API feature. The caller sends a trends.google.com/trends/explore URL through a zone. Optional flags brd_json=1 and brd_trends=timeseries,geo_map ask for widgets instead of raw HTML. Geo, date, category, language, and gprop are query params on that URL. The product is a fetch. Trends API is not a fetch. It is mode plus source plus keyword. Docs sit on the API reference.

A Trends URL through a SERP zone

Docs show two transports. REST posts to https://api.brightdata.com/request with zone, url, and format. Proxy examples use brd.superproxy.io and a brd-customer-...-zone-... user. Async variants return a job id.

The mental model is "open this Google URL from a clean IP." That is useful when the rest of the stack already speaks zones. It is waste when the only needed object is a dated 0-100 series. Trends API never takes a Trends URL. Sending https://trends.google.com/... as keyword is a bad call.

brd_json is still Explore

timeseries and geo_map are Google widgets. They are not Trends API fields. value on a Trends API row is a 0-100 index for the requested source. Bright Data's JSON is whatever the page emitted that day.

Date tokens on the URL match Google (now 1-d, today 12-m, custom ranges). Trends API growth uses percent_growth presets such as 12M, YTD, and MTD. Those strings are not Bright Data date tokens. Mixing them fails both products.

Proxy credentials versus a trend score

A Bright Data key unlocks a zone. A Trends API key unlocks three modes. The first key does not know source=tiktok. The second key does not know brd_trends. Zone plus URL versus source plus keyword is on Trends API vs Bright Data.

No zone name. No brd_json. For a live Google list, switch mode to get_top_trends and type to Google Trends. Parse the body string.

What the JSON still is

Keep Bright Data when anti-bot and SERP coverage are already on the invoice and Trends is one more URL. Check Bright Data's current SERP pricing. Leave when the dashboard must join Google to Wikipedia pageviews or Steam without standing up a second scrape target. A named Explore scrape with a target field is Decodo. A GET engine for the same website is SerpApi.