Channel
@OzonSellerAPI
On this record: Topic · Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry
4,835subscribers
+43 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001619444339 |
|---|---|
| Type | Channel |
| Username | @OzonSellerAPI |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 13 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/OzonSellerAPI |
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 13 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 00:19 | 4,835 | +19 |
| 11 Sept 2026, 13:37 | 4,816 | +16 |
| 6 Sept 2026, 23:01 | 4,800 | +10 |
| 2 Sept 2026, 18:56 | 4,790 | -2 |
| 31 Aug 2026, 01:47 | 4,792 | -8 |
| 27 Aug 2026, 23:48 | 4,800 | -4 |
| 24 Aug 2026, 21:54 | 4,804 | +5 |
| 21 Aug 2026, 03:02 | 4,799 | +3 |
| 18 Aug 2026, 04:45 | 4,796 | +6 |
| 14 Aug 2026, 21:58 | 4,790 | +2 |
| 11 Aug 2026, 13:35 | 4,788 | -4 |
| 7 Aug 2026, 07:00 | 4,792 | no change |
| 7 Aug 2026, 07:00 | 4,792 | first reading |
21 posts held, back to 10 June 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 8 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 21 posts for this entry, the most recent from 11 August 2026. An engagement rate over an empty window would be a number about nothing.
62 reactions across 21 posts, in 5 distinct kinds. The most used accounts for 56.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👀 | 35 | 56.5% | |
| 👍 | 17 | 27.4% | |
| ❤ | 5 | 8.06% | |
| 🔥 | 3 | 4.84% | |
| ✍ | 2 | 3.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 62 reactions 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.
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
Ozon Доставка для продавцов: поддержка расчета предварительной стоимости доставки Мы обновили метод v2/delivery/checkout в Seller API. Теперь вы можете получать не только предварительные сроки доставки, но и стоимость услуг. Подробнее по ссылке
👀3
Обратите внимание! Сегодня, 6 августа 2026 года, мы проводим плановую очистку пула связок. Будет удалено ещё 31 100 неактуальных связок. Пожалуйста, проверьте ваши интеграции на предмет возможных изменений.
👀1
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
30 июля 2026 /v1/finance/accrual/by-day: Обновили описание параметров date и last_id в запросе метода. В ответе метода: добавили параметр accruals.container_fees; обновили описание параметров accruals.accrued_category и last_id.
👀3❤1
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
Изменение валидации атрибута 23536 - «Нужен код маркировки» в Seller API Важные обновления в работе с атрибутами и новым функционалом маркировки. Подробнее по ссылке
👀1
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: Добавили пара…
👍2❤1👀1
21 июля 2026 /v1/finance/accrual/by-day: Обновили описание параметра accruals.posting.products.delivery.services в ответе метода. В разделе Частые ошибки добавили описание ошибки PRODUCT_IS_ARCHIVED для метода /v2/products/stocks.
👀1
Обновление справочника ТН ВЭД: чистка некорректных связок 23 июля мы проводим техническое обслуживание справочника ТН ВЭД. Мы удаляем порядка 55 000 неактуальных связок «значение ТН ВЭД — категория». Подробнее по ссылке
👀2
Методы для работы с отгрузками по схеме FBS Информируем вас о предстоящем переходе метода /v1/analytics/stocks на работу с данными в режиме реального времени. В настоящий момент данные обновляются дважды в сутки (в 07:00 и 16:00 по UTC). 17 августа метод перейдет на работу в режиме реального времени. Пожалуйста, подготовьте свои системы к изменениям, чтобы переход на новый формат данных прошел бесшовно.
👀4👍1
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.
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“Ozon Seller API notification” (@OzonSellerAPI), 4,835 subscribers as measured 15 September 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.