Telegram RegisterThe public register of Telegram
Telegram profile photo for Bybit API Announcements

Channel

Bybit API Announcements

@Bybit_API_Announcements

Verified by Telegram

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

2,977subscribers

-29 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-1001184826830
TypeChannel
Username@Bybit_API_Announcements
CreatedBetween 1 March 2018 and 31 July 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live12 October 2026
Measurements held17
Confirmed unchanged1 time, most recently 12 October 2026
On Telegramt.me/Bybit_API_Announcements

Topic

Crypto & trading — 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 15 September 2026 and assigned it the closest of 31 fixed categories, at 99% 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

2,9763,0062,9916 August 2026 — 3,006 subscribers7 August 2026 — 3,006 subscribers11 August 2026 — 3,004 subscribers14 August 2026 — 3,001 subscribers17 August 2026 — 2,997 subscribers20 August 2026 — 2,995 subscribers24 August 2026 — 2,999 subscribers27 August 2026 — 2,995 subscribers30 August 2026 — 2,992 subscribers2 September 2026 — 2,989 subscribers6 September 2026 — 2,982 subscribers10 September 2026 — 2,976 subscribers14 September 2026 — 2,977 subscribers18 September 2026 — 2,981 subscribers27 September 2026 — 2,979 subscribers5 October 2026 — 2,983 subscribers12 October 2026 — 2,977 subscribers2,9776 August 202612 October 2026
17 measurements spanning 67 days, net -29. 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 2,972–3,011 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Oct 2026, 16:202,977-6
5 Oct 2026, 17:172,983+4
27 Sept 2026, 19:372,979-2
18 Sept 2026, 13:552,981+4
14 Sept 2026, 12:542,977+1
10 Sept 2026, 17:142,976-6
6 Sept 2026, 00:422,982-7
2 Sept 2026, 03:242,989-3
30 Aug 2026, 02:442,992-3
27 Aug 2026, 12:552,995-4
24 Aug 2026, 04:252,999+4
20 Aug 2026, 14:222,995-2
17 Aug 2026, 19:332,997-4
14 Aug 2026, 08:253,001-3
11 Aug 2026, 05:283,004-2
7 Aug 2026, 00:003,006no change
6 Aug 2026, 23:563,006first reading

Engagement

20 posts held, back to 27 May 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 3 pages 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Recent posts

6 Aug 2026, 08:19 UTC270 viewsread 8 August 2026
File

Dear Traders, To increase market liquidity and improve your trading experience, Bybit will adjust the tick size for selected Perpetual Contracts and Spot Pairs on Aug 11, 2026, 8:30 AM UTC. Please refer to the documents for full details. We recommend reviewing your risk tolerance and trading strategy to ensure they align with the new tick size changes.

5 Aug 2026, 06:52 UTC320 viewsread 8 August 2026

🚀 HYPE Options Expansion!! We're excited to announce the launch of HYPE Options. Following the initial launch, more HYPEUSDT Options contracts will be available on Aug 6, 8AM UTC, including expiries on: Aug 8, Aug 9, Aug 14, Aug 21, Aug 28 & Sep 25. From Aug 7 onwards, HYPE Options will be listed on a regular basis, giving you more expiries and greater trading flexibility. Trade Now: https://www.bybit.com/en/trade…

3 Aug 2026, 02:52 UTC445 viewsread 8 August 2026

Dear Traders, As it almost has been one year since the Classic Spot Account was officially discontinued, Bybit will deprecate below endpoints used to query historical Classic Spot order and trade data in order to reduce maintenance costs. If you require access to this historical data, please download it from the Bybit website: https://www.bybit.com/en/user/assets/exportStatment Affected Endpoints - Get Pre-upgrade…

31 Jul 2026, 10:36 UTC514 viewsread 8 August 2026

Dear Traders, Following further internal review, the planned update to the smpGroup field has been revised. Instead of changing the data type from int32 to int64 as previously announced (https://t.me/Bybit_API_Announcements/428), smpGroup will now be changed from int32 to string. Mainnet: August 6, 2026 Affected APIs: 1. GET /v5/order/realtime - https://bybit-exchange.github.io/docs/v5/order/open-order 2. GET /v5…

30 Jul 2026, 11:08 UTC477 viewsread 8 August 2026

Dear Traders, Bybit is expanding RPI (Retail Price Improvement) order access across Spot and Perpetuals markets, allowing more users to place RPI orders. Starting Jul 30, 2026, RPI orders will be available on all RPI-enabled symbols for institutional users and retail users placing orders via API. Please refer to: https://announcements.bybit.com/en/article/expanded-rpi-order-access-on-bybit-spot-and-perpetuals--art…

30 Jul 2026, 03:04 UTC497 viewsread 8 August 2026

[API UPDATE] Full Orderbook Supports Futures The Futures Full Orderbook will soon be available via both of the following interfaces: * REST API : https://bybit-exchange.github.io/docs/v5/market/full-ob * WebSocket : https://bybit-exchange.github.io/docs/v5/websocket/public/full-ob Release Schedule * Testnet: 4 Aug * Mainnet:11 Aug If you plan to leverage these enhancements, please update your integration accordi…

23 Jul 2026, 10:17 UTC649 viewsread 8 August 2026

Dear Traders, A new `execType` enum value, `CorporateAction`, has been added. This enum will be used for U.S. equity perpetual contracts to identify executions generated by corporate actions, including stock splits and reverse stock splits. Backend support for this enum is now in place. It will only be returned when applicable corporate action events occur. Clients are encouraged to update their integrations in ad…

20 Jul 2026, 11:51 UTC639 viewsread 8 August 2026

Delisting of CBK,FLIP,FUEL,OL,PAAL,SAROS,STREAM Deposits for CBK,FLIP,FUEL,OL,PAAL,SAROS,STREAM will close after Jul 22, 2026, 8:00AM UTC. Spot Trading of these pairs will end after Jul 23, 2026, 8:00AM UTC, and all open orders will be automatically removed. For more information, please refer to https://announcements.bybit.com/en/article/delisting-of-cbk-flip-fuel-ol-paal-saros-stream--artc357601e1303/?category=del…

20 Jul 2026, 04:22 UTC637 viewsread 8 August 2026

Dear Traders, Due to an expansion of the field capacity, the `smpGroup` field will be upgraded from int32 to int64. Go-live Date: July 30, 2026 Please ensure your applications are updated accordingly to support the new data type and maintain compatibility. Affected APIs: 1. GET /v5/order/realtime https://bybit-exchange.github.io/docs/v5/order/open-order 2. GET /v5/order/history https://bybit-exchange.github.io/d…

17 Jul 2026, 10:24 UTC601 viewsread 8 August 2026

Dear traders, Bybit will be delisting the PUMPBTCUSDT, WHITEWHALEUSDT, HIGHUSDT Perpetual Contract at Jul 20, 2026, 9:00AM UTC. All active orders and conditional orders will be automatically canceled. Any open positions in these Perpetual Contracts will be automatically closed and the closing price will be based on the average index price 30 minutes prior to the delisting. For more information , please refer to ht…

15 Jul 2026, 09:07 UTC573 viewsread 8 August 2026

Dear Traders Moonriver (MOVR) & Moonbeam (GLMR) networks termination and migration to Base Network Key Timeline 20 Jul, 8AM UTC - Closure of deposit and withdrawal of MOVR through Moonriver and GLMR through Moonbeam. 22 Jul, 8AM UTC - Reopen of deposit and withdrawal of MOVR and GLMR through Base. New smart contract addresses on Base * MOVR: 0x43fEB74608334DDa8c1a6500D185cFC3Ea962B83 * GLMR: 0xB3846fD356c2149ee8D3…

6 Jul 2026, 03:09 UTC758 viewsread 8 August 2026

Dear Traders, To align the behavior of the Open API with the Bybit frontend, we will be updating the logic of the Get Master Account Deposit Address API. What’s changing? The API will now return the selected deposit address with the highest priority. If no address has been selected, it will return the earliest created deposit address by default. Will this affect you? You will not be affected if: * You have never …

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

“Bybit API Announcements” (@Bybit_API_Announcements), 2,977 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/Bybit_API_Announcements.

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.