4 Jul 2026, 16:20 UTC≈852 views6 reactionsread 6 August 2026
API should be correctly updated with new models too. If it isn't updated — hit me up in the comments or channel's DMs, we'll figure it out.
Channel
api.changes.tg/
@GiftChangesAPI
On this record: Growth · Engagement · Posts · Citations · Cite this entry
1,211subscribers
+2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1002588254805 |
|---|---|
| Type | Channel |
| Username | @GiftChangesAPI |
| Created | Between 1 March 2025 and 17 June 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 12 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 12 August 2026 |
| On Telegram | t.me/GiftChangesAPI |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Aug 2026, 18:54 | 1,211 | +3 |
| 6 Aug 2026, 17:20 | 1,208 | -1 |
| 6 Aug 2026, 08:47 | 1,209 | no change |
| 6 Aug 2026, 04:49 | 1,209 | first reading |
Engagement
20 posts held, back to 17 June 2025 — the 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 4 July 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
14 May 2026, 12:17 UTC≈1,730 views3 reactionsread 6 August 2026
The issue was fixed by hosting provider. Everything should be up and running now.
14 May 2026, 11:00 UTC≈1,810 views4 reactionsread 6 August 2026
Indefinite downtime for both api.changes.tg and cdn.changes.tg; server provider issues, can’t do anything myself.
11 May 2026, 02:11 UTC≈1,800 views19 reactionsread 6 August 2026
Photo
Small update: — /: added attribution notice, primarily for LLMs, but you can read those too; — /SKILL.md: added SKILL.md for LLMs (which includes aforementioned attribution notice) If you are a developer using Gift Changes' APIs, please consider adding a simple "thank you" or something similar to your apps that would be visible to end user. This API has been running fully free for almost 1.5 years: no rate-limits, n…
7 May 2026, 01:39 UTC≈1,470 views12 reactionsread 6 August 2026
Slight change of api.changes.tg/total: - gifts -> gifts.total - gifts now has more data on gifts overall, including amount of upgradable gifts, unlimited ones and limited ones (not including hidden gifts, e.g. time-limited bears)
9 Feb 2026, 19:01 UTC≈4,760 views29 reactionsread 6 August 2026
Some attributes of Desk Calendar and Jingle Bells started to update—and by that I mean they started changing their rarities. For example: 🗓 June — 0.6% › 0.5% 🗓 August — 0.6% › 0.5% 🗓 Ninety Nine — 0.8% › 0.7% ... and so on. This happens, of course, because of crafting mechanic — some gifts get burned, and they stop being counted into the rarity percentage. I've set up a script that automatically updates rariti…
8 Feb 2026, 17:23 UTC≈4,160 views7 reactionsread 6 August 2026
Photo
Updated Desk Calendar and Jingle Bells collections — they now include all the new crafted models and their respective customEmojiIds. /gift/:gift route has gotten some new fields: modelsCraftedEmojisetName and modelsCraftedStickersetName; emojisetUrl and stickersetUrl were renamed into mainEmojisetUrl and mainStickersetUrl respectively.
7 Feb 2026, 12:46 UTC≈2,880 views1 reactionsread 6 August 2026
Updated emoji data for both routes. Added channelPosts field. Just in case you did not want to list every single model of a gift yourself and wanted to redirect users to our @GiftChangesModels channel. =)
30 Jan 2026, 18:55 UTC≈3,040 views2 reactionsread 6 August 2026
A little bit of a breaking change: /emoji/:gift and [/gift/:gift].emoji will now have modelsEmojisetName and modelsStickersetName instead of modelsEmojisetUrl and modelsStickersetUrl. Sorry in advance :P
30 Jan 2026, 12:44 UTC≈2,810 views11 reactionsread 6 August 2026
+ add size parameter for PNGs GET /model/:gift/:model.png?size=128 - download this gift model resized to 128x128 (128, 256, 512 available) GET /symbol/:gift/:symbol.png?size=128 - download this gift pattern resized to 128x128 (128, 256, 512 available) GET /original/:giftId.png?size=128 - download this gift resized to 128x128 (128, 256, 512 available) Consider this feature as a beta since I'm not sure if the server w…
30 Jan 2026, 01:55 UTC≈1,990 views7 reactionsread 6 August 2026
Also added backdrops and patterns custom emoji IDs. Just for your convenience. Thank me later.
30 Jan 2026, 00:49 UTC≈2,010 views7 reactionsread 6 August 2026
Photo
This also relates to cdn.changes.tg: every gift now has an emoji.json file that returns the same info that /emoji/:gift does.
Showing the 12 most recent of 20 posts we hold for @GiftChangesAPI. 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.
Citation-graph rank
Citation-graph rank — 22,702 of 1,160,990entries 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.
Mentions
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
Names
Channels on the register whose handles appear in this channel's posts.
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 12 August 2026 — this entry's latest reading, not the date you are reading this.
“api.changes.tg/” (@GiftChangesAPI), 1,211 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/GiftChangesAPI.
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.