Channel
@yandex_market_api
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
2,653subscribers
+21 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001807554716 |
|---|---|
| Type | Channel |
| Username | @yandex_market_api |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 8 September 2026 |
| Measurements held | 11 |
| Confirmed unchanged | 1 time, most recently 8 September 2026 |
| On Telegram | t.me/yandex_market_api |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 16:39 | 2,653 | +1 |
| 3 Sept 2026, 12:39 | 2,652 | +4 |
| 31 Aug 2026, 01:43 | 2,648 | +6 |
| 28 Aug 2026, 00:33 | 2,642 | -4 |
| 24 Aug 2026, 17:16 | 2,646 | +5 |
| 20 Aug 2026, 15:26 | 2,641 | +5 |
| 17 Aug 2026, 11:47 | 2,636 | -1 |
| 13 Aug 2026, 13:38 | 2,637 | +5 |
| 10 Aug 2026, 12:28 | 2,632 | -2 |
| 7 Aug 2026, 18:42 | 2,634 | +2 |
| 7 Aug 2026, 10:17 | 2,632 | first reading |
20 posts held, back to 21 April 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 2 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 5 August 2026. An engagement rate over an empty window would be a number about nothing.
115 reactions across 20 posts, in 18 distinct kinds. The most used accounts for 24.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 28 | 24.3% | |
| 👍 | 27 | 23.5% | |
| ❤ | 17 | 14.8% | |
| 👎 | 16 | 13.9% | |
| 🤣 | 6 | 5.22% | |
| 🤔 | 4 | 3.48% | |
| 👀 | 3 | 2.61% | |
| 👌 | 3 | 2.61% | |
| 🎉 | 2 | 1.74% | |
| ✍ | 1 | 0.87% | |
| 🎃 | 1 | 0.87% | |
| 🏆 | 1 | 0.87% | |
| 💯 | 1 | 0.87% | |
| 🗿 | 1 | 0.87% | |
| 🙈 | 1 | 0.87% | |
| 🤝 | 1 | 0.87% | |
| 🦄 | 1 | 0.87% | |
| 🫡 | 1 | 0.87% |
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 20 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 115 reactions 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 21 April 2026 to 5 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.
4 августа 🔸 POST v2/campaigns/{campaignId}/offers/stocks POST v3/businesses/{businessId}/offers/stocks Изменили максимальное значение параметра limit с 200 до 100, значение по умолчанию — с 100 до 50. Если передано значение больше 100, оно обрезается до 100, ошибка валидации не возвращается.
👎14🤣5👍1💯1🦄1🙈1
29 июля 🔸 POST v3/businesses/{businessId}/warehouses POST v3/businesses/{businessId}/offers/stocks POST v3/businesses/{businessId}/offers/stocks/update POST v3/businesses/{businessId}/warehouse/models/status POST v3/businesses/{businessId}/reports/stocks/generate Передача остатков через API Работа со складами Добавили методы для работы со складами и остатками на уровне кабинета: получение списка складов, просмотр и…
👍3🔥1
16 июля 🔸 GET v2/campaigns/{campaignId}/settings В ответе метода добавили объект taxation с информацией о налогообложении партнера: ставку НДС vat. Поддерживаемые значения ставки: VAT_22, VAT_12, VAT_10, VAT_07, VAT_05 и NO_VAT.
👍3🤝1
🔸 Расскажите про работу с Маркетом через интеграции Поделитесь мнением в небольшом опросе. Ответы займут не более 5 минут и помогут сделать работу через модули ещё удобнее для вас. Пройти опрос Если вы не можете ответить на вопросы сами, перешлите пост знающему сотруднику.
👍4👌3
22 июня 🔸 POST v1/businesses/{businessId}/orders POST v2/campaigns/{campaignId}/orders/{orderId}/deliverDigitalGoods Обработка заказов с цифровыми товарами В ответах методов получения заказов у объекта delivery добавили поле digitalGoods с информацией о способе доставки цифрового товара: тип (EMAIL, ACTIVATION_CODE, STEAM_GIFT или CHAT) и ссылка steamLink на Steam-аккаунт покупателя (только для типа STEAM_GIFT). Пер…
👍5
Работайте через API с отзывами на товары ваших брендов С 18 июня рекламодатели могут работать с отзывами на товары не только в личном кабинете, но и через API. Чтобы получать отзывы используйте метод POST /v1/businesses/{businessId}/goods-feedback-advertiser. Для обработки отзывов рекламодателей передайте параметр sourceType=ADVERTISER в методах: — POST v2/businesses/{businessId}/goods-feedback/comments; — POST v…
🔥4❤2
17 июня 🔸 GET v2/campaigns/{campaignId}/orders/{orderId}POST v1/businesses/{businessId}/orders Добавили новый подстатус заказа PURCHASE_GROUP_THRESHOLD_NOT_REACHED_CANCELLED — заказ участвовал в групповой покупке и был отменен, потому что не было достигнуто нужное количество покупок.
🔥4
15 июня 🔸 POST v2/campaigns/{campaignId}/offers/update POST v2/campaigns/{campaignId}/offers Удалили устаревший параметр quantum — настройку продажи квантами. 🔸 POST v1/businesses/{businessId}/orders В товары заказа добавили поле itemStatuses. В нем возвращается информация о статусах отдельных единиц товара.
🔥2
10 июня 🔸 POST v2/campaigns/{campaignId}/offersPOST v2/businesses/{businessId}/offer-mappings Добавили новый статус товара: READY_FOR_PUBLICATION. Статус устанавливается, если товар Готов к продаже, но магазин еще не завершил подключение.
👍1
2 июня 🔸 POST v1/businesses/{businessId}/reports/marketing-detalization/generate Добавили новый метод для генерации отчета по счету маркетинга. 🔸 POST v2/reports/closure-documents/detalization/generate Из параметра contractType удалили значение MARKETING. Для генерации отчета по счету маркетинга используйте POST v1/businesses/{businessId}/reports/marketing-detalization/generate.
❤1🔥1
Начните работать с отчётами рекламодателей через API 3 июня 2026 обновили интеграцию, чтобы вы могли автоматизировать сбор информации по всем рекламным каналам и обрабатывать её удобным для вас способом. Теперь по API можно работать с отчётами рекламодателей: по счёту маркетинга, охватному продвижению, полкам, бусту показов и продаж. Чтобы сформировать нужный отчёт, начните передавать параметр sourceType = ADVERTIS…
🔥4👍1
Обновления в API 🔸POST v1/campaigns/{campaignId}/orders/create Добавили параметр fake в запрос создания заказа по модели LAAS. Он позволяет проверить работу магазина и его API на тестовых заказах; такой заказ не будет отгружен и не влияет на остатки. 🔸 Методы отчётов Изменили доступы к отчётам: для генерации отчётов достаточно read-only доступов API-Key-токена.
👍4🔥1
Showing the 12 most recent of 20 posts we hold for @yandex_market_api. 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.
Named by 1 registered channel — 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.
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 8 September 2026 — this entry's latest reading, not the date you are reading this.
“API Яндекс Маркета” (@yandex_market_api), 2,653 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/yandex_market_api.
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.