Telegram RegisterThe public register of Telegram
Telegram profile photo for Hazex API

Channel

Hazex API

@HazexAPI

On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry

403subscribers

-2 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001932295836
TypeChannel
Username@HazexAPI
CreatedBetween 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live16 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 16 August 2026
On Telegramt.me/HazexAPI

Growth

4034054048 August 2026 — 405 subscribers8 August 2026 — 405 subscribers16 August 2026 — 403 subscribers8 August 202616 August 2026
3 measurements spanning 8 days, net -2. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 403–405 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
16 Aug 2026, 07:58403-2
8 Aug 2026, 15:27405no change
8 Aug 2026, 10:04405first reading

Engagement

20 posts held, back to 13 July 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 31 December 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

346 reactions across 20 posts, in 16 distinct kinds. The most used accounts for 23.1% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
8023.1%
👍6318.2%
custom 52220799544218182674412.7%
custom 54314118629503885103811.0%
🔥308.67%
custom 5897501460509234625298.38%
custom 5431766464040283359195.49%
🥰113.18%
custom 545630953496223464792.60%
👏72.02%
custom 539568906087642675061.73%
custom 520860192184520872430.867%
custom 628284292841918344930.867%
🤩20.578%
custom 521330550803478338410.289%
🆒10.289%

Custom emoji. 9 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them areTelegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 20 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 346reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 13 July 2024 to 31 December 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Telegram Stars

Stars received
5
across the posts below
Posts paid on
2
of 20 we hold a reading for · 10%
Most on one post
3
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @HazexAPI. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 13 July 2024 to 31 December 2025. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

31 Dec 2025, 05:07 UTC819 views13 reactionsread 8 August 2026

⚡ Join Group Chat to get more APIs and source codes from other users 👉 Join @HazexApiChat

5👍4🔥4

31 Dec 2025, 05:04 UTC801 views10 reactionsread 8 August 2026

📔 API Name: Anime Search and Download 🔗 API URL: https://api.hazex.sbs/anime ✨ Action: Search by text and download anime and manga in mp4 🔻 Request Method: GET (JSON) 🔮 Parameters: ├ mode: Mode to perform action ├ q: Query to search (search) └ downloadUrl: URL From search mode to get mp4 video (download) 👉 Modes: search & download 💠 Examples: ▫️Search: https://api.hazex.sbs/anime?mode=search&q=SearchQuery ▫️

6🔥2👍1🆒1

30 Dec 2025, 05:14 UTC715 views8 reactionsread 8 August 2026

🚀 Need an API but can’t scrape it yourself? If you want an API but are unable to scrape the website, just send me the source link and I’ll try to extract the API and list it in this channel. 💬 Send here: Hazex API Let’s make APIs accessible for everyone 💡

4🔥4

4 Sept 2025, 07:19 UTC≈1,770 views24 reactionsread 8 August 2026

📔 API Name: Vehicle Info (RTO) 🔗 API URL: https://api2.hazex.sbs/rc-info ✨ Action: Fetch complete vehicle information instantly, including registration details, owner info, and vehicle specifications (Indian) 🔻 Request Method: GET (JSON) 🔮 Parameters: └ number: Vehicle Registration Number 🔻 Example: https://api2.hazex.sbs/rc-info?number=NUMBER ©️ Copy Claims By: @HazexAPI 💬 Support Chat: @HazexApiChat

9custom 54563095349622346479custom 52220799544218182675custom 54317664640402833591

30 Jun 2025, 05:38 UTC≈1,960 views14 reactionsread 8 August 2026

📔 API Name: YouTube Video Summarizer 🔗 API URL: https://api.hazex.sbs/yt-summarizer ✨ Action: Summarize any YouTube video into clear, concise text with support for word limit control 🔻 Request Method: GET (JSON) 🔮 Parameters: ├ url: YouTube Video URL ├ wordCount: Word Limit (min: 15, max: 1000)* └ language: Summary Language (Df: English) 🔻 Example: https://api.hazex.sbs/yt-summarizer?url=https://youtube.com/w

7custom 52086019218452087243custom 54317664640402833593custom 52133055080347833841

29 Jun 2025, 09:25 UTC≈1,760 views13 reactionsread 8 August 2026

📔 API Name: AI Detector 🔗 API URL: https://api.hazex.sbs/ai-detector ✨ Action: Detect whether content is written by AI or a human, with confidence scores and breakdowns 🔻 Request Method: GET or POST (JSON) 🔮 Parameters: └ text: Text To Be Detected 🔻 Example: https://api.hazex.sbs/ai-detector?text=TEXT ©️ Copy Claims By: @HazexAPI 💬 Support Chat: @HazexApiChat

custom 54317664640402833595custom 589750146050923462542custom 52220799544218182672

29 Jun 2025, 09:02 UTC≈1,630 views16 reactionsread 8 August 2026

📔 API Name: YouTube Video Transcribe 🔗 API URL: https://api.hazex.sbs/yt-transcribe ✨ Action: Transcribe any YouTube video into text with speaker separation and timestamped subtitles 🔻 Request Method: GET (JSON) 🔮 Parameters: └ url: YouTube Video URL 🔻 Example: https://api.hazex.sbs/yt-transcribe?url=https://youtube.com/watch?v=xyz ©️ Copy Claims By: @HazexAPI 💬 Support Chat: @HazexApiChat

custom 589750146050923462573custom 54317664640402833593custom 54314118629503885102custom 52220799544218182671

27 Jun 2025, 08:18 UTC≈1,520 views16 reactionsread 8 August 2026

📔 API Name: Text To Speech 🔗 API URL: https://api.hazex.sbs/tts ✨ Action: Convert text to speech with multi-language, multi-voice support 🔻 Request Method: GET - Query params POST - JSON or Form-Data 🔺 Response in JSON 🔮 Parameters: ├ text: Text to convert into Speech └ voice: Name of Voice Models (Def: Andrew) 🎙 Voice Models: Andrew, Ava, Brian, Emma, Remy, Vivienne, Florian, Seraphina, Giuseppe, Thalita 🔻

custom 54317664640402833597custom 589750146050923462532custom 52220799544218182672custom 54314118629503885102

30 Oct 2024, 15:20 UTC≈2,870 views33 reactionsread 8 August 2026

📔 API Name: Search Engine API 🔗 API URL: https://search-engine.hazex.workers.dev/ ✨ Action: Search Websites and Images From Server of Search Engine 🔻 Request Method: GET (JSON) 🔮 Parameters: ├ q: Query * ├ safe: Safe Search [ on | off ] └ type: Search Type (Df: web) ├ web: Search Websites └ images: Search Images ├ filter: Image Filter (Only for images) └ region: Search Region (Only for web) 🔻

👍12custom 52220799544218182679custom 589750146050923462553custom 54314118629503885103🔥1

30 Oct 2024, 04:19 UTC≈2,410 views16 reactionsread 8 August 2026

🟢 Working Again

custom 58975014605092346258👍53

18 Oct 2024, 11:34 UTC≈2,590 views32 reactions2 Starsread 8 August 2026

🥰 Your Reactions Matter! Show some love to help us keep our services running and continue offering unique APIs for free!

custom 543141186295038851016👍63🔥2🥰2custom 58975014605092346252👏1

Showing the 12 most recent of 20 posts we hold for @HazexAPI. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Citation-graph rank

Citation-graph rank — 484,164 of 1,584,420entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 4 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 16 August 2026 — this entry's latest reading, not the date you are reading this.

“Hazex API” (@HazexAPI), 403 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/HazexAPI.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.