Telegram RegisterThe public register of Telegram
Telegram profile photo for MetaApi

Channel

MetaApi

@metaapi_cloud

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

1,483subscribers

+22 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001331666947
TypeChannel
Username@metaapi_cloud
CreatedBetween 1 March 2018 and 30 June 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live23 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/metaapi_cloud

Growth

1,4611,4831,4727 August 2026 — 1,461 subscribers7 August 2026 — 1,461 subscribers8 August 2026 — 1,462 subscribers10 August 2026 — 1,466 subscribers13 August 2026 — 1,470 subscribers16 August 2026 — 1,475 subscribers19 August 2026 — 1,477 subscribers23 August 2026 — 1,483 subscribers7 August 202623 August 2026
8 measurements spanning 16 days, net +22. 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 1,458–1,486 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 06:561,483+6
19 Aug 2026, 17:121,477+2
16 Aug 2026, 20:371,475+5
13 Aug 2026, 16:171,470+4
10 Aug 2026, 22:221,466+4
8 Aug 2026, 05:431,462+1
7 Aug 2026, 22:011,461no change
7 Aug 2026, 12:091,461first reading

Engagement

20 posts held, back to 12 December 2021the 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 22 August 2024. An engagement rate over an empty window would be a number about nothing.

Reaction mix

8 reactions across 3 posts, in 2 distinct kinds. The most used accounts for 87.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
787.5%
👍112.5%

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 3 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 8reactions 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 12 December 2021 to 22 August 2024, 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

22 Aug 2024, 18:32 UTC≈3,870 views6 reactionsread 7 August 2026

🔥We've released the brand new dashboard with many improvements and bugfixes. Feel free to let us know what you think via our support chat.

5👍1

21 Jul 2024, 15:59 UTC≈4,290 viewsread 7 August 2026

🔥We are happy to release a feature which allows to request a dedicated IP for a trading account you launch on MetaApi. The feature is available in web UI, javascript and python SDKs.

4 Dec 2023, 15:15 UTC≈7,620 viewsread 7 August 2026

❗️Please note that starting from Dec 4th, 2023 automatic deposits over $25 needs to be manually approved by our users. If you use auto deposit feature then you will receive an email notification containing instructions when it is time for automatic deposit.

2 Oct 2023, 16:54 UTC≈7,490 views1 reactionsread 7 August 2026

❗️We plan a backward incompatible update for risk management API. In order to avoid your application from being affected please follow the instructions below: - if your application is using javascript or python SDK we provide, please upgrade to the latest SDK version - if your application is using REST API, please follow instructions in this document https://metaapi.cloud/docs/risk-management/breakingChanges/

1

17 Aug 2023, 13:20 UTC≈6,370 views1 reactionsread 7 August 2026

💡With MetaApi you can protect your deployment from a major regional failure by deploying account replicas in a different spare region. The account replicas are billed at a 50% discounted rate.

1

2 Aug 2023, 20:06 UTC≈5,510 viewsread 7 August 2026

We recently upgraded API access token permission system to meet the needs of the most demanding applications. 🎉 ❗️Note that legacy account access tokens, returned by REST API in the trading account json payload are now deprecated. We will remove support for legacy account access tokens on Saturday, Sep 2nd. Please upgrade your apps if needed to use token management API instead in order to generate new account access

24 Jul 2023, 13:58 UTC≈4,240 viewsread 7 August 2026

❗️ If you are an extended subscription user and would like to use dedicated front-end server option, please make sure to enable the feature on this page https://app.metaapi.cloud/token/dedicated-frontend-server

9 Jul 2023, 06:27 UTC≈3,970 viewsread 7 August 2026

We've refactored our javascript SDK to make it super-easy to use full power of our SDK in modern UI frameworks. React, Vue.js and Angular code examples included in the release. Hope you'll enjoy the update! 🎉 https://github.com/metaapi/metaapi-javascript-sdk

13 May 2023, 11:04 UTC≈3,810 viewsread 7 August 2026

We've just launched tokyo region for users who want to use brokers hosting their servers in Asia. 🎉 The new region provides less than 1ms network latency to brokers hosting their servers in Tokyo area. 💪 Hope you'll enjoy reduced network latency while trading via brokers like this.

25 Apr 2023, 04:35 UTC≈3,540 viewsread 7 August 2026

Do you know that your users can configure their trading account themselves, so that you do not have to collect and store the trading account password on your side? Please check the feature in our docs: - REST API: https://metaapi.cloud/docs/provisioning/api/account/createAccount/#securely-configuring-trading-account-by-end-user - SDK: https://github.com/metaapi/metaapi-javascript-sdk/blob/master/docs/metaApi/managin

6 Nov 2022, 15:38 UTC≈3,840 viewsread 7 August 2026

We've just launched singapore region for users who want to use brokers which host their servers in Asia. 🎉 Now you can enjoy reduced network latency trading via brokers like this.

15 Oct 2022, 17:07 UTC≈3,900 viewsread 7 August 2026

We've released an update for risk management API and SDK 🎉. The updated version provides additional tools for proprietary trading firms, such as streaming of real-time equity, balance, drawdown, profit and trading challenge status to your app or dashboard. https://github.com/metaapi/metaapi-javascript-sdk/blob/master/docs/riskManagement.md

Showing the 12 most recent of 20 posts we hold for @metaapi_cloud. 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 23 August 2026 — this entry's latest reading, not the date you are reading this.

“MetaApi” (@metaapi_cloud), 1,483 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/metaapi_cloud.

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.