Telegram RegisterThe public register of Telegram
Telegram profile photo for CallerAPI

Channel

CallerAPI

@probivapi

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

922subscribers

-4 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-1002083373581
TypeChannel
Username@probivapi
CreatedBetween 1 November 2023 and 18 April 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live25 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/probivapi

Growth

922927924.57 August 2026 — 926 subscribers8 August 2026 — 926 subscribers8 August 2026 — 927 subscribers16 August 2026 — 924 subscribers25 August 2026 — 922 subscribers7 August 202625 August 2026
5 measurements spanning 18 days, net -4. 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 921–928 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 02:54922-2
16 Aug 2026, 18:13924-3
8 Aug 2026, 08:08927+1
8 Aug 2026, 00:51926no change
7 Aug 2026, 12:19926first reading

Engagement

20 posts held, back to 18 April 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 19 July 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

219 reactions across 19 posts, in 16 distinct kinds. The most used accounts for 62.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥13762.6%
👍177.76%
125.48%
🤝104.57%
👏94.11%
🤯94.11%
❤‍🔥52.28%
👎52.28%
💩41.83%
👾20.913%
🖕20.913%
😍20.913%
🥰20.913%
🆒10.457%
👌10.457%
😁10.457%

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 19 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 219reactions 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 18 April 2024 to 19 July 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.

Recent posts

19 Jul 2025, 09:29 UTC≈5,670 views8 reactionsread 8 August 2026

Launched a new module for HLR lookups: https://callerapi.com/carrier-lookup-api

🔥61👎1

25 Mar 2025, 21:41 UTC≈7,770 views6 reactionsread 8 August 2026

RU: Отличный туториал по подключению CallerAPI к Make EN: Great tutorial explaining how to connect CallerAPI to Make https://www.youtube.com/watch?v=8lBTKx055no

🔥51

14 Dec 2024, 18:53 UTC≈9,910 views6 reactionsread 8 August 2026

RU: Проблемы с интернациональными платежами были починены. Мы сменили платежную систему и теперь доступны карты Visa, MasterCard, etc.! EN: All the payment issues were fixed. We migrated away from GoCardless and now support credit/debit cards like Visa, MasterCard, etc.!

👏6

13 Dec 2024, 21:10 UTC≈8,910 views9 reactionsread 8 August 2026

RU: Мы испытываем проблемы с платежной системой GoCardless, через банковский перевод. Извиняемся за неудобства En: We are experiencing problems and instability in our payment provider GoCardless. Bank transfer is not currently available. Sorry for the inconvenience

🤝8👾1

5 Oct 2024, 18:54 UTC≈11,200 views23 reactionsread 8 August 2026
Photo

RU: Большой апдейт сайта и API! Теперь абсолютно новый дизайн, API стабильнее, и скоро будет апгрейд инфраструктуры и сервера Также, теперь у нас есть официальные enterprise партнеры которые предоставили нам больше данных, они будут интегрированы в следующих апдейтах EN: Major website and API update! We did a user interface revamp, the API is more stable, and soon we will introduce an infrastructure and server up

👍5🔥54💩4👎3🖕2

2 Sept 2024, 15:30 UTC≈10,100 views9 reactionsread 8 August 2026
Photo

RU: CallerAPI теперь интегрирован с Zapier! Ищу заинтересованые бизнесы которые хотели бы протестировать и получить бесплатно 5000 запросов, подать заявку можно тут: https://callerapi.com/contacts EN: CallerAPI is now integrated with Zapier! I'm searching for businesses who would like to test it and receive 5000 credits for free. If you are interested, feel free to contact us: https://callerapi.com/contacts

👏3👍2❤‍🔥1🔥1😁1🆒1

1 Sept 2024, 09:42 UTC≈7,540 views5 reactionsread 8 August 2026
Photo

RU: В личном кабинете теперь есть виджет с проверкой индивидуального номера и загрузка CSV! Скоро будут сделаны интеграции для всех упомянутых платформ в прошлом посте! EN: A new dashboard widget came out today which allows single phone number enrichment and bulk enrichment by uploading a CSV! Soon all the integrations mentioned above will be released, stay tuned!

🔥5

30 Aug 2024, 17:24 UTC≈6,630 views1 reactionsread 8 August 2026
Poll

RU: Какая интеграция CallerAPI нужна больше для твоего бизнеса? EN: Which CallerAPI integration would benefit your business?

  1. AMO CRM28%
  2. HubSpot3%
  3. Monday11%
  4. Salesforce3%
  5. Pipedream2%
  6. Zapier25%
  7. Make6%
  8. Custom (in comments 💬)23%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

👍1

5 Aug 2024, 13:33 UTC≈7,370 views16 reactionsread 8 August 2026
Photo

Да… пришлось сделать rebranding, а то Швейцарцы очень не одобрили название ProbivAPI, пришлось объяснять им в чем прикол названия. Зато фронтенд сильно улучшили, теперь он приемлемо выглядит Еще раз прошли проверку GDPR, на всякий случай и юристы все одобрили Скоро будем сильно расширятся в Европу и Америку, так что будет опция оплаты не только криптой, а еще и картой Посты будут на двух языках, на Русском и на Ан

🤯9👍31👌1👎1🥰1

1 Aug 2024, 20:14 UTC≈6,590 views14 reactionsread 8 August 2026

Спасибо всем за 500 🔥 Рост проекта невероятный, я очень хотел проект превратить из просто поделки в Энтерпрайз решение, но не ожидал такого мощного роста! В честь этого я решил отблагодарить тебя сотней запросов в апи, вот ссылка Следующие обновления в API будут очень крутыми, сейчас работаем над системой парсинга мобильных номеров из любого текста, это нужно для генерации лидов Потом, будет добавлен сам поиск эт

🔥122

29 Jul 2024, 16:54 UTC≈5,540 views12 reactionsread 8 August 2026

Сегодня ввели вторую оптимизацию и смогли повысить скорость ответа API в 2 раза! Раньше: 1.6 секунд Сейчас: 0.8 секунд Протестировано из Швейцарии, Нидерландов и Испании. Следующий апдейт будет очень не стандартный… будем делать CRM для cold calling (телемаркетинг) По статистики enterprise и premium клиентов, 85% пытаются построить свой собственный CRM для телемаркетинга, соответственно надо помочь всем бизнесам

🔥10❤‍🔥2

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

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

30 Aug 2024, 17:24 UTCAnonymous Poll141 voters

RU: Какая интеграция CallerAPI нужна больше для твоего бизнеса? EN: Which CallerAPI integration would benefit your business?

  1. AMO CRM28%
  2. HubSpot3%
  3. Monday11%
  4. Salesforce3%
  5. Pipedream2%
  6. Zapier25%
  7. Make6%
  8. Custom (in comments 💬)23%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 20 most recent posts we hold, published 18 April 2024 to 19 July 2025. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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

“CallerAPI” (@probivapi), 922 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/probivapi.

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.