Telegram RegisterThe public register of Telegram
Telegram profile photo for API-CLOUD - Облачное API

Channel

API-CLOUD - Облачное API

@apicloudru

On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry

216subscribers

+7 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001295880450
TypeChannel
Username@apicloudru
CreatedBetween 1 April 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live11 October 2026
Measurements held8
Confirmed unchanged1 time, most recently 11 October 2026
On Telegramt.me/apicloudru

Topic

Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 24 September 2026 and assigned it the closest of 31 fixed categories, at 96% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

2092192147 August 2026 — 209 subscribers8 August 2026 — 209 subscribers16 August 2026 — 211 subscribers31 August 2026 — 214 subscribers9 September 2026 — 213 subscribers16 September 2026 — 215 subscribers1 October 2026 — 219 subscribers11 October 2026 — 216 subscribers2167 August 202611 October 2026
8 measurements spanning 65 days, net +7. 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 208–221 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Oct 2026, 17:59216-3
1 Oct 2026, 13:37219+4
16 Sept 2026, 03:39215+2
9 Sept 2026, 02:55213-1
31 Aug 2026, 15:04214+3
16 Aug 2026, 16:18211+2
8 Aug 2026, 11:04209no change
7 Aug 2026, 20:13209first reading

Engagement

20 posts held, back to 15 April 2026 — 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 page of 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 9 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

30 reactions across 14 posts, in 3 distinct kinds. The most used accounts for 50.0% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥1550.0%
👍1240.0%
😱310.0%

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 14 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 30 reactions 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 15 April 2026 to 9 July 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

9 Jul 2026, 04:30 UTC137 viewsread 8 August 2026

Обновление API gibdd В тестовом режиме запущен метод driverv2 для проверки водительских удостоверений.

7 Jul 2026, 19:03 UTC153 viewsread 8 August 2026

Обновление API rsa Метод osago: Добавлен параметр type_vu в котором можно передать тип водительского удостоверения.

22 Jun 2026, 09:57 UTC238 viewsread 8 August 2026

Обновление API rsa В методе запроса 'osago' добавлена дополнительная проверка на наличие физического лица в полисе ОСАГО.

13 Jun 2026, 07:55 UTC301 views1 reactionsread 8 August 2026

API МВД, метод rkl: С сайта МВД пропала проверка в Реестре контролируемых лиц. Вернется или нет - не известно. Воспользуйтесь рабочим методом rklv2

😱1

9 Jun 2026, 18:31 UTC308 views3 reactionsread 8 August 2026

Обновление платформы API-CLOUD: Полезная фишка для Юридических лиц: Автоматический запрос счета при достижении баланса определенной суммы. Устанавливаете порог баланса и сумму счета. И когда баланс приблизится к порогу, сервис самостоятельно создаст запрос на получение счета и направит его в бухгалтерию. Включить можно в разделе Настройки > Уведомления и рассылка

👍2🔥1

1 Jun 2026, 13:16 UTC327 viewsread 8 August 2026

Обновление API sudrf Метод case: В результат добавлен массив appeal (Обжалование решений, определений)

31 May 2026, 17:42 UTC334 viewsread 8 August 2026

Обновление API pb_nalog Добавлен метод search_upr_uchr (Поиск по Участие в ЮЛ). Позволяет получить Сведения о лице, имеющем право без доверенности действовать от имени юридического лица и Сведения об учредителях (участниках, единственном акционере) юридического лица

31 May 2026, 13:34 UTC300 views3 reactionsread 8 August 2026

Обновление платформы API-CLOUD: Запущен новый API ЕАИСТО (проверка диагностических карт, пробега) Подробнее в документации https://api-cloud.ru/eaisto

👍3

28 May 2026, 10:26 UTC317 views2 reactionsread 8 August 2026

Обновление API sudrf Метод case: Добавили в результат массив enforcement_orders (Судебные листы) и маcсив actList (Судебные акты)

👍2

27 May 2026, 19:25 UTC304 views2 reactionsread 8 August 2026

Обновление API fgisTaxi Запущен новый API (v2): - Перевозчики теперь привязаны к авто, добавлен массив carriers в котором будут собраны все перевозчики. - Ускорена обработка - Обновлена документация Старый метод будет работать до 01.08.2026. Необходим перевод вашего кода на новую версию, после указанной даты старая версия перестанет работать.

👍2

17 May 2026, 10:29 UTC314 views2 reactionsread 8 August 2026

Обновление API gost Запущен новый API (v2): - Поддержка нескольких отзывных компаний по одному vin (все результаты добавляются в массив result) - В результате появился ключ passing (статус прохождения отзывной компании) - Добавлена ключ urlGost (ссылка на новость об отзывной кампании) - Добавлен ключ found (флаг результат поиска) - Улучшена обработка - Обновлена документация Старый метод будет работать до 01.08.2026…

🔥2

Showing the 12 most recent of 20 posts we hold for @apicloudru. 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.

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 11 October 2026 — this entry's latest reading, not the date you are reading this.

“API-CLOUD - Облачное API” (@apicloudru), 216 subscribers as measured 11 October 2026. Telegram Register, tgregister.com/channel/apicloudru.

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.