Call Trends API from Haxe with haxe.Http

A Haxe 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 Haxe library. haxe.Http and haxe.Json ship in the standard library. haxe.Json.parse reads the envelope, then parses the body string a second time. Pulled on 2026-10-26, Google Search for haxe programming scored 12.0 for the week of 2026-10-24, flat versus 12.0. haxe language scored 12.0, down 25.0% from 16.0. Those two tokens closed at the same 12.0, with opposite 7D signs. YouTube for haxe programming scored 0.0 versus 0.0. Do not copy bare haxe Search 58.0 onto a language-adoption alert that only watches the phrase token at 12.0. The same helper that stores those rows also pulls a live Google Trends board. A rank-18 name that weekly Search printed at 100.0 versus 1.0 is documented in BioWare live rank versus weekly Search.

How does a Haxe 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":"haxe programming","percent_growth":["7D","30D","3M","12M"]}

class Main {
  static function main() {
    var key = Sys.getEnv("TRENDSAPI_API_KEY");
    var req = new haxe.Http("https://api.trendsapi.ai/api");
    req.setHeader("Authorization", "Bearer " + key);
    req.setHeader("Content-Type", "application/json");
    req.setPostData("{\"mode\":\"get_growth\",\"source\":\"google search\",\"keyword\":\"haxe programming\",\"percent_growth\":[\"7D\",\"30D\",\"3M\",\"12M\"]}");
    req.onData = function(data) {
      var envelope:Dynamic = haxe.Json.parse(data);
      var inner:Dynamic = haxe.Json.parse(envelope.body);
      trace(inner.results);
    };
    req.onError = function(err) {
      trace(err);
    };
    req.request(true);
  }
}

new haxe.Http takes the URL. setHeader sets the Bearer key and content type. setPostData holds the JSON body. request(true) sends POST. haxe.Json.parse on the transport bytes, then haxe.Json.parse again on the body string. The sample uses Sys.getEnv and is for a sys target. Docs live at:

https://api.haxe.org/haxe/Http.html
https://api.haxe.org/haxe/Json.html
https://api.haxe.org/Sys.html
https://haxe.org

haxe.Http and haxe.Json are in the standard library. That is the client, not a Trends API source. There is no haxelib install step for this sample.

The response envelope is {"statusCode": int, "body": string}. body is a JSON string and must be parsed a second time before reading recent_value. A Gleam client that does the same double parse with gleam_httpc is on Gleam Trends API. A Zig client is on Zig Trends API.

What did get_growth return for Haxe language tokens?

get_growth for haxe programming on google search tips on 2026-10-24. Store the exact strings. haxe language is a different series. Both phrases closed at 12.0 on the same week, with opposite 7D signs.

get_time_series for haxe programming on Google Search closed at 12 on 2026-10-24, matching get_growth 12.0. Adjacent weeks: 12 on 2026-10-17, 0 on 2026-10-10, 0 on 2026-10-03, 0 on 2026-09-26. Peak in this pull is 100 on 2023-06-17. Tip 12 is not that June 2023 high. The payload marked data_quality low with a warning that the underlying signal is over 90% zeros. The payload printed growth 999999 on 14D, 30D, 3M, 12M, and YTD because those baselines were 0.0. Report 12.0 versus 0.0. 7D printed 0.0% versus 12.0, the opposite sign from haxe language 7D -25.0% versus 16.0.

haxe language closed at 12.0, down 25.0% from 16.0. Opposite 7D sign from haxe programming, same close. Later windows baselined at 0.0. Report 12.0 versus 0.0. Do not copy programming 7D 0.0% onto language -25.0%.

haxelib closed at 6.0, down 25.0% from 8.0, 6 points below programming 12.0. The payload marked data_quality low. Later windows baselined at 0.0. Report 6.0 versus 0.0. That string is not package-download volume.

haxe compiler closed at 0.0 versus 0.0 on every window, also data_quality low. Store the zeros. Do not copy compiler 0.0 onto programming 12.0.

Bare haxe closed at 58.0, down 4.92% from 61.0. 14D was 58.0 versus 59.0 (-1.69%). 30D was 58.0 versus 65.0 (-10.77%). 3M was 58.0 versus 42.0 (+38.1%). 12M was 58.0 versus 56.0 (+3.57%). YTD was 58.0 versus 45.0 (+28.89%). That four-character string mixes other uses of the word. Do not treat Search 58.0 as Haxe language adoption. There is no haxelib source on this API.

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

haxe programming 12.0 sat 11 points below rust programming 23.0 and 4 points below zig programming 16.0. It sat 5 points above gleam programming 7.0. haxe language 12.0 matched the programming close and sat 4 points below zig. Do not copy rust 23.0 onto haxe programming 12.0. A prior calendar-day pull on this same Saturday tip printed gleam programming at 7.0 versus 6.0. Today that neighbor reprinted to 7.0 versus 5.0. zig programming reprinted from 16.0 versus 20.0 to 16.0 versus 16.0. hare programming reprinted from 7.0 versus 8.0 to 6.0 versus 5.0. Store the session pull. Same-tip reprints are not a new week. This pull is still the 2026-10-24 Saturday tip. A Hare Trends API helper stores the systems-language neighbor on the same 7D window. A Nim Trends API helper stores nim programming.

What did YouTube, News, and Wikipedia return?

YouTube for haxe programming printed zeros on every growth window. Keyword Google News for both Haxe phrases printed zeros. Wikipedia titles resolve on their own. Compare Wikipedia on volume.

YouTube for haxe programming tipped 0.0 on 2026-10-24 versus 0.0, while Search sat at 12.0. The payload marked data_quality low. get_time_series closed at 0, matching get_growth. Adjacent weeks were also 0. Peak in this pull is 100 on 2022-08-06. That is a single non-zero YouTube point. On 2023-06-17 Search printed 100 while YouTube printed 0. On 2022-08-06 YouTube printed 100 while Search printed 0. YouTube 0.0 is not Search 12.0. Do not treat the YouTube floor as language adoption while Search sits at 12.0 after a 100 close in June 2023.

YouTube for haxe language closed at 0.0 versus 0.0 on every window, also data_quality low. Store the zeros. Do not copy language YouTube 0.0 onto programming Search 12.0.

Bare haxe YouTube closed at 62.0, up 14.81% from 54.0. 12M was 62.0 versus 63.0 (-1.59%). That is not the phrase series. Do not copy bare YouTube 62.0 onto programming YouTube 0.0.

Keyword Google News for haxe programming printed 0.0 versus 0.0 on every window, also data_quality low. Store the zeros. Keyword Google News for haxe language printed 0.0 versus 0.0 on every window, also data_quality low. Do not fill News from Search 12.0. Keyword News and the Google News Top News board are different feeds. Mode docs sit at https://trendsapi.ai/docs.

Wikipedia for short title Haxe resolved. September 2026 scored 3.2 with 1,724 pageviews versus August 8.5 with 2,048 (volume -15.82%). 3M was 3.2 / 1,724 versus June 5.3 / 1,849 (volume -6.76%). 12M was 3.2 / 1,724 versus September 2025 11.5 / 2,231 (volume -22.73%). YTD was 3.2 / 1,724 versus January 24.1 / 3,007 (volume -42.67%). 7D and 14D collapsed (collapsed_range: recent and baseline resolved to the same monthly point). Peak in this pull is 100.0 / 7,687 in November 2021. Parenthetical title Haxe (programming language) resolved to a different page. September scored 13.3 with 24 pageviews versus August 11.0 with 20 (volume +20.0%). Peak on that title is 100.0 / 181 in November 2021. Do not join 1,724 views onto Search 12.0. Do not treat parenthetical-title Haxe (programming language) at 24 views as the language page. The short title is the finding. That is the opposite of Gleam, where the language title was the high-volume page. Wikipedia source docs sit at https://trendsapi.ai/trends/wikipedia-trends.

There is no haxelib source on this API. npm covers npmjs. python covers PyPI. A Haxe watchlist that wants package downloads has no third source to join onto Search 12.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. The rank snapshot can stamp at the same second as the mover snapshot, or two hours earlier.

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-10-26T10:01:37Z the live Google Trends board ranked bioware at 18. The 1-day rank_change sort stamped the same second, returned 25 rows (baseline 2026-10-25T02:01:34Z), and omitted that token. The 7-day sort returned 1 row (baseline 2026-10-19T02:01:34Z): kylie jenner at +37 from 107. Weekly Search for bioware scored 100.0 versus 1.0, up 9900.0%. YouTube also scored 100.0 versus 1.0. The helper that stores those rows is the blog in this batch: BioWare live rank versus weekly Search. The same live board ranked php at 8 with weekly Search 100.0 versus 22.0 and estimated volume 2,270,000. Do not copy php 100.0 onto haxe programming 12.0. 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. Five language tokens plus one live board is 6 calls. A Monday run that also pulls YouTube and Wikipedia for the programming phrase is 8 calls. Four weeks is 32 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 haxe, haxe programming, haxe language, and haxelib as separate series.
4. Compare Wikipedia Haxe on volume at 1,724 September views, not parenthetical-title Haxe (programming language) at 24.
5. Pair get_top_trends rank with both rank_change windows and get_growth on the exact board string.