Channel
@wb_api_notifications
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry
9,688subscribers
+3 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1002085684952 |
|---|---|
| Type | Channel |
| Username | @wb_api_notifications |
| Description | Официальный канал портала разработчиков Wildberries — WB API Обновления • Новости • Кейсы для бизнеса и разработчиков 📄 Документация: dev.wildberries.ru 💬 Сообщество: dev.wildberries.ru/forum |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 1 time, most recently 11 August 2026 |
| On Telegram | t.me/wb_api_notifications |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 04:21 | 9,688 | +3 |
| 7 Aug 2026, 12:31 | 9,685 | no change |
| 7 Aug 2026, 12:22 | 9,685 | first reading |
23 posts held, back to 25 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 14 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 12 August 2026 |
|---|---|
| Posts held | 23 (25 June 2026 – 12 August 2026) |
| Views total | 39,540 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 14:53 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.
Lifetime counters from Telegram’s own channel header, read 12 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
#promotion Рекомендованные ставки для CPC-кампаний Добавили отображение рекомендованных ставок для CPC-кампаний — по предложениям пользователей в Сообществе WB API. Теперь метод GET /api/advert/v0/bids/recommendations возвращает рекомендованные ставки не только для кампаний с типом оплаты CPM за показы, но и для CPC — за клики. 📖 Журнал изменений WB API 💬 Сообщество WB API С уважением, команда WB API 🔗 Читайте …
#fbs Изменения в заказах FBS С 18 августа добавить номер декларации на товары (ДТ) можно будет только к сборочным заданиям в статусе confirm. Также с 18 августа продавцам из Армении будет обязательно указывать номер ДТ для товаров, произведённых вне ЕАЭС, если заказ из Армении доставляется в РФ. Чтобы проверить, обязательно ли закреплять номер ДТ за сборочным заданием, используйте метод GET /api/v3/orders/new. Об…
#dbs #in_store_pickup Изменения в сборочных заданиях DBS и Самовывоз Добавили методы получения данных о ценах продавца без учёта скидок и суммах к оплате покупателем с учетом всех скидок и кэшбека по ID сборочных заданий: • DBS — POST /api/marketplace/v3/dbs/orders/final-price • Самовывоз — POST /api/marketplace/v3/click-collect/orders/final-price Для расчётов используйте суммы к оплате покупателем из ответов новы…
#analytics #reports Лента заказов в WB API Получить отчёт Лента заказов теперь можно с помощью WB API — методом POST /api/analytics/v1/order-feed. Используйте его в качестве замены методов: • GET /api/v1/supplier/orders — Заказы • GET /api/v1/supplier/sales — Продажи Делитесь с нами обратной связью в Сообществе WB API. На основе ваших комментариев мы сможем сделать переход на новый метод максимально комфортным. Ме…
Posted without readable text
#fbs Перенесли дату обновления на ночь с 5 по 6 августа. Напоминаем, что метод GET /api/v3/orders будет возвращать информацию только о сборочных заданиях, созданных менее 3 месяцев назад. Получить сборочные задания, созданные более 3 месяцев назад, вы сможете только методом GET /api/marketplace/v3/fbs/orders/archive. 📖 Журнал изменений WB API 💬 Сообщество WB API С уважением, команда WB API 🔗 Читайте в МАКС Move…
#items Изменение в методах работы со складами продавца С 5 августа с помощью API нельзя будет создавать и редактировать склады продавца для сверхгабаритных товаров (СГТ). Данная возможность будет только в личном кабинете. Что изменится в методах: • Получить список складов WB — GET /api/v3/offices — в ответе теперь не будут возвращаться СГТ-склады WB • Создать склад продавца — POST /api/v3/warehouses — при создании…
#fbs Настройки автовозврата для заказов FBS Добавили методы для работы с автовозвратами FBS для малогабаритных товаров — "cargoType":1 — по предложениям пользователей в Сообществе WB API. Теперь с помощью WB API вы можете: • Получить настройки автовозврата продавца — GET /api/marketplace/v3/fbs/settings/autoreturns • Обновить настройки автовозврата продавца — PATCH /api/marketplace/v3/fbs/settings/autoreturns • По…
#promotion Изменения в сервисе Продвижения В ответ метода GET /api/advert/v1/config добавили информацию о минимальной сумме пополнения бюджета кампании — поле minTopUp. 📖 Журнал изменений WB API 💬 Сообщество WB API С уважением, команда WB API 🔗 Читайте в МАКС Changes in Promotion service In the response of the GET /api/advert/v1/config added the minTopUp field — information about the minimum campaign budget to…
#analytics Новая версия Оценки товара и отключение метода Скрытые из каталога Добавили новую версию метода получения отчёта Оценка товара — POST /api/analytics/v2/item-rating. C её помощью вы можете получать данные отдельно по скрытым из каталога товарам. В новом методе: • добавили параметр onlyShadowedNms: • укажите true, чтобы получить в отчёте только скрытые из каталога товары • укажите false, чтобы получ…
#dbs #in_store_pickup Изменения в заказах DBS и Самовывоз Обновили методы WB API согласно анонсу от 2 июля. Теперь, при закреплении за сборочными заданиями номеров деклараций на товары (ДТ), обязательно указывать код страны происхождения товара по Общероссийскому классификатору стран мира для B2B-заказов DBS и Самовывоз. Без корректного кода страны закрепить за сборочным заданием номер ДТ невозможно. 📖 Журнал изме…
#promotion Изменения в сервисе Продвижения В ответ метода GET /api/advert/v2/adverts добавили признак возможности изменения списка товаров в кампании поле — can_change_nms в объекте restrictions. 📖 Журнал изменений WB API 💬 Сообщество WB API С уважением, команда WB API Changes in Promotion service Added the can_change_nms field to the restrictions object in the response of the GET /api/advert/v2/adverts method…
Showing the 12 most recent of 23 posts we hold for @wb_api_notifications. 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.
Citation-graph rank — 150,627 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.
Named by 3 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“ВБ Интеграция | WB API” (@wb_api_notifications), 9,688 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/wb_api_notifications.
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.