Shopping intent is the Google Shopping property, not the web box. source google shopping and source google search accept the same phrase and do not share a 0-100. POST https://api.trendsapi.ai/api. Two source strings on one POST. Both are listed on the API reference. Property split: the Google Trends guide. Compare recent_value after the second decode.
Two scores, one phrase
POST https://api.trendsapi.ai/api
Authorization: Bearer <api_key>
Content-Type: application/json
{"mode":"get_growth","source":"google shopping, google search","keyword":"air fryer","percent_growth":["7D","1M","3M","12M"]}
Property split on 27 Aug 2026 for air fryer (both recent dates 22 Aug 2026):
| Source | Recent | 7D | 1M | 3M | 12M |
|---|---|---|---|---|---|
google search |
56 | −3.45% | +5.66% | −18.84% | +16.67% |
google shopping |
8 | +33.33% | +33.33% | −84.31% | +100% |
Search is a research-and-brand property. Shopping is closer to a product card. Agency notes in 2026 still put comparison and "best X" queries on Search, and visual category queries on Shopping. The table is that split as numbers. Shopping's 3M cliff (8 vs 51) is the off-season. Shopping's 7D lift (8 vs 6) is people back in the aisle this week. Search did not join the 7D lift.
Feed matching, not a keyword list
Standard Shopping campaigns still match queries from titles, descriptions, product type, and GTIN. There is no positive keyword bid. This API does not write the feed. It tells the feed owner whether Shopping interest for a phrase is rising. If google shopping 7D is up and the title lacks the phrase, the feed is late. If google search is up and Shopping is flat, the demand is still in research.
volume_weighted_growth in the four-source product pull used search, TikTok, and Amazon. Shopping had no volume in that weight. Do not treat a missing Shopping volume as zero demand. Read recent_value. Amazon notes: the Amazon guide.