Telegram RegisterThe public register of Telegram
Telegram profile photo for Ozon Seller API notification

Channel

Ozon Seller API notification

@OzonSellerAPI

Verified by Telegram

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

4,804subscribers

+12 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001619444339
TypeChannel
Username@OzonSellerAPI
CreatedBetween 1 December 2021 and 30 April 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live24 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/OzonSellerAPI

Growth

4,7884,8044,7967 August 2026 — 4,792 subscribers7 August 2026 — 4,792 subscribers11 August 2026 — 4,788 subscribers14 August 2026 — 4,790 subscribers18 August 2026 — 4,796 subscribers21 August 2026 — 4,799 subscribers24 August 2026 — 4,804 subscribers7 August 202624 August 2026
7 measurements spanning 18 days, net +12. 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 4,786–4,806 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 21:544,804+5
21 Aug 2026, 03:024,799+3
18 Aug 2026, 04:454,796+6
14 Aug 2026, 21:584,790+2
11 Aug 2026, 13:354,788-4
7 Aug 2026, 07:004,792no change
7 Aug 2026, 07:004,792first reading

Engagement

21 posts held, back to 10 June 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 8 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
36.5%
avg views ÷ 4,804 subscribers
Avg views / post
1,750
6 posts measured
Reaction rate
0.124%
reactions ÷ views · ER floor
Posts in window
6
of 21 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 11 August 2026
Posts held21 (10 June 202611 August 2026)
Views total10,514
Reactions total13
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken12 Aug 2026, 05:19 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Reaction mix

62 reactions across 21 posts, in 5 distinct kinds. The most used accounts for 56.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👀3556.5%
👍1727.4%
58.06%
🔥34.84%
23.23%

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 21 of the 21 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 62reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 21 most recent posts we hold, published 10 June 2026 to 11 August 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

11 Aug 2026, 12:20 UTC984 views2 reactionsread 12 August 2026

11 августа 2026 /v1/supply-order/act/summary/get; /v1/supply-order/act/product/get; /v1/supply-order/act/accept; /v1/supply-order/act/accept/status: Добавили бета-методы для работы с актами FBO. /v2/returns/rfbs/get: Отметили устаревшим параметр returns.return_method_description в ответе метода. /v2/returns/rfbs/reject; /v2/returns/rfbs/compensate; /v2/returns/rfbs/verify; /v2/returns/rfbs/receive-return; /v2/retu

1👀1

6 Aug 2026, 12:52 UTC≈2,170 views3 reactionsread 12 August 2026

Ozon Доставка для продавцов: поддержка расчета предварительной стоимости доставки Мы обновили метод v2/delivery/checkout в Seller API. Теперь вы можете получать не только предварительные сроки доставки, но и стоимость услуг. Подробнее по ссылке

👀3

6 Aug 2026, 11:06 UTC≈2,080 views1 reactionsread 12 August 2026

Обратите внимание! Сегодня, 6 августа 2026 года, мы проводим плановую очистку пула связок. Будет удалено ещё 31 100 неактуальных связок. Пожалуйста, проверьте ваши интеграции на предмет возможных изменений.

👀1

5 Aug 2026, 10:10 UTC≈1,960 views2 reactionsread 12 August 2026

4 августа 2026 /v1/notification/set; /v1/notification/update: Обновили описание параметра types в запросе методов. /v1/notification/list: Обновили описание параметра urls.types.type в ответе метода. /v1/notification/push-type/list: Обновили описание параметра types.type в ответе метода. /v4/posting/fbs/unfulfilled/list; /v4/posting/fbs/list; /v3/posting/fbo/list: Обновили описание параметра postings.products.is_m

👀1👍1

5 Aug 2026, 10:05 UTC≈1,680 views4 reactionsread 12 August 2026

30 июля 2026 /v1/finance/accrual/by-day: Обновили описание параметров date и last_id в запросе метода. В ответе метода: добавили параметр accruals.container_fees; обновили описание параметров accruals.accrued_category и last_id.

👀31

5 Aug 2026, 10:04 UTC≈1,640 views1 reactionsread 12 August 2026

28 июля 2026 /v1/report/info: Добавили параметр result.additional_data в ответ метода. /v1/report/list: Добавили параметр result.reports.additional_data в ответ метода. /v1/finance/realization/posting: Обновили описание параметра message в теле ошибки 400 метода. /v1/report/realization/posting/create: Добавили бета-метод для получения позаказного отчёта о реализации товаров.

👀1

24 Jul 2026, 09:04 UTC≈3,050 views1 reactionsread 12 August 2026

Изменение валидации атрибута 23536 - «Нужен код маркировки» в Seller API Важные обновления в работе с атрибутами и новым функционалом маркировки. Подробнее по ссылке

👀1

23 Jul 2026, 10:12 UTC≈3,480 views4 reactionsread 12 August 2026

22 июля 2026 /v3/posting/fbs/list: Добавили параметр filter.integration_type_flow в запрос метода. Добавили параметры result.postings.integration_type_flow и result.postings.sorting_center в ответ метода. /v4/posting/fbs/list: Добавили параметр filter.integration_type_flow в запрос метода. Добавили параметры postings.integration_type_flow и postings.sorting_center в ответ метода. /v3/posting/fbs/get: Добавили пара

👍21👀1

23 Jul 2026, 10:12 UTC≈2,970 views1 reactionsread 12 August 2026

21 июля 2026 /v1/finance/accrual/by-day: Обновили описание параметра accruals.posting.products.delivery.services в ответе метода. В разделе Частые ошибки добавили описание ошибки PRODUCT_IS_ARCHIVED для метода /v2/products/stocks.

👀1

23 Jul 2026, 10:10 UTC≈2,440 views2 reactionsread 12 August 2026

Обновление справочника ТН ВЭД: чистка некорректных связок 23 июля мы проводим техническое обслуживание справочника ТН ВЭД. Мы удаляем порядка 55 000 неактуальных связок «значение ТН ВЭД — категория». Подробнее по ссылке

👀2

20 Jul 2026, 12:26 UTC≈3,190 views5 reactionsread 12 August 2026

Методы для работы с отгрузками по схеме FBS Информируем вас о предстоящем переходе метода /v1/analytics/stocks на работу с данными в режиме реального времени. В настоящий момент данные обновляются дважды в сутки (в 07:00 и 16:00 по UTC). 17 августа метод перейдет на работу в режиме реального времени. Пожалуйста, подготовьте свои системы к изменениям, чтобы переход на новый формат данных прошел бесшовно.

👀4👍1

15 Jul 2026, 09:05 UTC≈4,030 views5 reactionsread 12 August 2026

14 июля 2026 /v3/finance/transaction/list; /v3/finance/transaction/totals: Методы устаревают и будут отключены 8 сентября 2026 года. Переключитесь на /v1/finance/accrual/postings, /v1/finance/accrual/types, /v1/finance/accrual/by-day.

👀5

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

“Ozon Seller API notification” (@OzonSellerAPI), 4,804 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/OzonSellerAPI.

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.