Call Trends API from PowerShell with Invoke-WebRequest

A PowerShell job talks to Trends API with one POST to https://api.trendsapi.ai/api, a Bearer key, and a JSON body that names a mode. There is no official PowerShell module. Invoke-WebRequest sends the request. ConvertFrom-Json parses the envelope, then parses the body string a second time. Pulled on 2026-09-24, Google Search for powershell scored 56.0 for the week of 2026-09-19, down 9.68% from 62.0. powershell programming scored 19.0, down 47.22% from 36.0. pwsh scored 64.0, down 4.48% from 67.0. windows powershell scored 54.0, down 3.57% from 56.0. Do not copy 64.0 or 54.0 onto powershell 56.0. Do not treat powershell 7 Search 26.0, down 33.33% from 39.0, as the shell string. The same helper that stores those rows also pulls a live Google Trends board; a rank-15 token that weekly Search printed at 43.0 versus 7.0 is documented in Giada live rank versus weekly Search.

How does a PowerShell client call Trends API?

POST https://api.trendsapi.ai/api
Authorization: Bearer <api_key>
Content-Type: application/json

{"mode":"get_growth","source":"google search","keyword":"powershell","percent_growth":["7D","30D","3M","12M"]}

$headers = @{
    Authorization = "Bearer $($env:TRENDSAPI_API_KEY)"
    "Content-Type" = "application/json"
}
$payload = '{"mode":"get_growth","source":"google search","keyword":"powershell","percent_growth":["7D","30D","3M","12M"]}'
$resp = Invoke-WebRequest -Uri "https://api.trendsapi.ai/api" -Method Post -Headers $headers -Body $payload
$envelope = $resp.Content | ConvertFrom-Json
# body is a JSON string; parse it a second time
$inner = $envelope.body | ConvertFrom-Json
$inner | ConvertTo-Json -Depth 8

Invoke-WebRequest and ConvertFrom-Json are the HTTP and JSON cmdlets used here. Cmdlet docs live at:

https://learn.microsoft.com/powershell/module/microsoft.powershell.utility/invoke-webrequest
https://learn.microsoft.com/powershell/module/microsoft.powershell.utility/convertfrom-json

The response envelope is {"statusCode": int, "body": string}. body is a JSON string and must be parsed a second time before reading recent_value. Invoke-RestMethod deserializes the transport JSON on its own, so the first parse is implicit and $response.body is still a string that needs ConvertFrom-Json. A C# client that does the same double parse with HttpClient is on C# Trends API. A Python client is on Python Trends API.

What did get_growth return for PowerShell language tokens?

get_growth for powershell on google search tips on 2026-09-19. Store the exact strings. The programming phrase, the pwsh binary, windows powershell, powershell core, and powershell 7 are different series.

get_time_series for powershell on Google Search closed at 56 on 2026-09-19, matching get_growth 56.0. Adjacent weeks: 62 on 2026-09-12, 66 on 2026-09-05, 52 on 2026-08-29, 54 on 2026-08-22. Peak in this pull is 100 on 2026-06-06, with 99 on 2026-06-20, 98 on 2026-06-27, and 95 on 2026-04-04. Tip 56 is a slide off that June 2026 high, not a new peak. 3M printed -43.43% versus 99.0. A job that alerts on YTD +60.0% versus 35.0 while 3M sits at -43.43% is reading a calendar rebound off the January 35 close, not a return to 100.

powershell programming closed at 19.0, down 47.22% from 36.0. 14D was 19.0 versus 46.0 (-58.7%). 30D was 19.0 versus 24.0 (-20.83%). 3M was 19.0 versus 81.0 (-76.54%). 12M was 19.0 versus 37.0 (-48.65%). YTD was 19.0 versus 21.0 (-9.52%). The programming phrase and the shell string do not share a 7D magnitude. Do not copy 56.0 onto 19.0.

pwsh closed at 64.0, down 4.48% from 67.0. 14D was 64.0 versus 74.0 (-13.51%). 30D was 64.0 versus 55.0 (+16.36%). 3M was 64.0 versus 100.0 (-36.0%). 12M was 64.0 versus 52.0 (+23.08%). YTD was 64.0 versus 31.0 (+106.45%). The binary token closed above the shell string on 7D and printed the opposite 12M sign (+23.08% versus -27.27%). Do not copy 64.0 onto powershell 56.0.

windows powershell closed at 54.0, down 3.57% from 56.0. 14D was 54.0 versus 53.0 (+1.89%). 7D and 14D signs diverge. 30D was 54.0 versus 47.0 (+14.89%). 3M was 54.0 versus 97.0 (-44.33%). 12M was 54.0 versus 62.0 (-12.9%). YTD was 54.0 versus 41.0 (+31.71%). That Windows-prefixed string is a different series from the shell string.

powershell core closed at 21.0, down 43.24% from 37.0. 14D was 21.0 versus 43.0 (-51.16%). 30D was 21.0 versus 21.0 (0.0%). 3M was 21.0 versus 86.0 (-75.58%). 12M was 21.0 versus 60.0 (-65.0%). YTD was 21.0 versus 29.0 (-27.59%). Do not treat a Core 7D -43.24% as the shell string.

powershell 7 closed at 26.0, down 33.33% from 39.0. 14D was 26.0 versus 35.0 (-25.71%). 30D was 26.0 versus 29.0 (-10.34%). 3M was 26.0 versus 78.0 (-66.67%). 12M was 26.0 versus 37.0 (-29.73%). YTD was 26.0 versus 20.0 (+30.0%). Do not treat a version 7D -33.33% as language adoption. The shell string closed at 56.0.

Neighbor languages on the same pull, same source, same 7D window:

Do not copy python programming 47.0 or csharp 53.0 onto powershell 56.0. csharp scored 53.0 versus 56.0 (-5.36%) while csharp programming scored 16.0 versus 5.0 (+220.0%). 3M, 12M, and YTD for csharp programming printed growth 999999 versus 0.0. Report 16.0 versus 0.0. Do not copy 53.0 onto 16.0, and do not copy 16.0 onto powershell 56.0. python programming YTD was 47.0 versus 21.0 (+123.81%). powershell YTD was 56.0 versus 35.0 (+60.0%). Same calendar, different YTD shape. f# programming YTD printed growth 999999 versus 0.0. Report 23.0 versus 0.0. bash programming 12M was 24.0 versus 31.0 (-22.58%). java programming 12M was 21.0 versus 38.0 (-44.74%). rust programming 12M was 16.0 versus 25.0 (-36.0%). An F# Trends API helper stores that neighbor on the same 7D window. A Rust Trends API helper stores rust programming the same way.

What did YouTube, News, and Wikipedia return?

YouTube for powershell printed a growth-versus-series mismatch. Keyword Google News printed a sparse series with a 7D flat print. Wikipedia titles resolve on their own. Compare Wikipedia on volume.

YouTube get_growth for powershell tipped 63.0 on 2026-09-19 versus 65.0 on 7D (-3.08%). 14D was 63.0 versus 59.0 (+6.78%). 30D was 63.0 versus 71.0 (-11.27%). 3M was 63.0 versus 73.0 (-13.7%). 12M was 63.0 versus 59.0 (+6.78%). YTD was 63.0 versus 48.0 (+31.25%). get_time_series closed at 62 on 2026-09-19. Adjacent week: 65 on 2026-09-12. Growth 63.0 disagreed with series close 62. Store both. Peak in this pull is 100 on 2025-12-13, with 76 on 2025-11-15, 2025-12-20, 2026-06-27, and 2026-07-11. Tip 62 is not that December 2025 spike. YouTube 63.0 is not Search 56.0. Do not treat a YouTube 7D -3.08% as the Search 7D -9.68%.

Keyword Google News for powershell tipped 12.0 versus 12.0 on 7D (0.0%). The payload marked data_quality low with a warning that the underlying signal is over 90% zeros. 14D was 12.0 versus 68.0 (-82.35%). 30D was 12.0 versus 52.0 (-76.92%). 3M, 12M, and YTD printed growth 999999 versus 0.0. Report 12.0 versus 0.0. Store the zeros and the 7D flat print. Do not fill News from Search 56.0. Keyword News and the Google News Top News board are different feeds. Mode docs sit at https://trendsapi.ai/docs.

Wikipedia for PowerShell resolved to Powershell. 7D and 14D collapsed (collapsed_range: recent and baseline resolved to the same monthly point). August 2026 scored 30.6 with 253 pageviews versus July 29.2 with 244 (score +4.79%, volume +3.69%). 3M was 30.6 / 253 versus May 29.7 / 247 (volume +2.43%). 12M was 30.6 / 253 versus August 2025 36.5 / 291 (volume -13.06%). YTD was 30.6 / 253 versus January 31.7 / 260 (volume -2.69%). Peak in this pull is 100.0 / 704 in May 2022, with 89.1 / 633 in January 2022 and 88.9 / 632 in April 2022. Tip 253 views is not that May 2022 high. Compare Wikipedia on volume. Do not join 253 views onto Search 56.0. Wikipedia source docs sit at https://trendsapi.ai/trends/wikipedia-trends.

There is no PowerShell Gallery registry source on this API. npm covers npmjs. python covers PyPI. A PowerShell watchlist that wants gallery downloads has no third source to join onto Search 56.0.

How does a watchlist store live boards next to weekly scores?

get_top_trends has no keyword. Pair the live Google Trends board with get_growth on the exact board string. Live rank, 1-day rank_change, and 7-day rank_change are three feeds.

POST https://api.trendsapi.ai/api
Authorization: Bearer <api_key>
Content-Type: application/json

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

On 2026-09-24T10:01:36Z the live Google Trends board ranked giada de laurentiis at 15. The 1-day rank_change sort returned 18 rows (baseline 2026-09-23T02:01:41Z) and printed +66 from prev_rank 81. The 7-day sort returned 19 rows (baseline 2026-09-17T02:01:38Z) and printed +118 from prev_rank 133. Weekly Search for that exact string scored 43.0 versus 7.0, up 514.29%. The helper that stores those rows is the blog in this batch: Giada live rank versus weekly Search. Board-shape notes for Google Trends live feeds sit at https://trendsapi.ai/trends/google-trends.

Free tier is 100 successful 200s per month. Only 200 responses count against quota. Six language tokens plus one live board is 7 calls. A Monday run that also pulls YouTube and Wikipedia for the shell string is 9 calls. Four weeks is 36 calls and still fits the free cap. Starter is 5,000, Pro 25,000, Business 100,000.

Envelope checklist

1. POST https://api.trendsapi.ai/api with Authorization: Bearer <api_key>.
2. Parse the transport JSON, then parse the body string a second time.
3. Store powershell, powershell programming, pwsh, windows powershell, powershell core, and powershell 7 as separate series.
4. Compare Wikipedia Powershell on volume (253 August views), not on 30.6.
5. Pair get_top_trends rank with both rank_change windows and get_growth on the exact board string.

A C# client that uses HttpClient for the same envelope is on C# Trends API.