Telegram RegisterThe public register of Telegram
Telegram profile photo for Dilovod API

Channel

Dilovod API

@dilovodapi

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

76subscribers

+2 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001528411798
TypeChannel
Username@dilovodapi
Created25 April 2023measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live23 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 23 August 2026
On Telegramt.me/dilovodapi

Growth

7476757 August 2026 — 74 subscribers8 August 2026 — 75 subscribers9 August 2026 — 75 subscribers23 August 2026 — 76 subscribers7 August 202623 August 2026
4 measurements spanning 16 days, net +2. 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 74–76 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
23 Aug 2026, 13:0476+1
9 Aug 2026, 21:3175no change
8 Aug 2026, 10:2075+1
7 Aug 2026, 20:5474first reading

Engagement

12 posts held, back to 25 April 2023the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 12 posts for this entry, the most recent from 18 June 2024. An engagement rate over an empty window would be a number about nothing.

Recent posts

18 Jun 2024, 15:33 UTC316 viewsread 9 August 2026

https://dilovod.crisp.help/uk/article/api-dilovod-1gwt3m0/#2-listmetadata-otrimannya-pereliku-metedanih-obyektiv

18 Jun 2024, 15:32 UTC307 viewsread 9 August 2026

Вийшла нова версія API 0.25 Додані методи: listMetadata: Отримання переліку метеданих об'єктів getMetadata: Отримання інформації про об'єкт метаданих

13 Jun 2024, 15:04 UTC327 viewsread 9 August 2026

Змінено адресу шлюза: https://api.dilovod.ua Стара адреса також працює.

20 Oct 2023, 10:46 UTC391 viewsread 9 August 2026

Як прискорити виконання запитів Ось деякі поради - якщо у запитах типу balance не вказувати дату, то будуть повернуті актуальні залишки, розрахунок яких швидше. - не використовуйте метод getObject у циклі, якщо потрібне лише читання реквізитів. Замість цього використовуйте прямий запит типу request. - звернення в декілька потоків заборонене - замість запиту окремих даних у циклі, користуйтеся різноманітними умовами

4 Oct 2023, 16:58 UTC366 viewsread 9 August 2026

Додано статтю https://dilovod.crisp.help/uk/article/api-dilovod-zapitannya-i-vidpovidi-lkkiux/?bust=1696438606523 Пропонуйте теми, які в вас викликали питання - додамо відповіді.

29 Sept 2023, 08:16 UTC331 viewsread 9 August 2026

Додано опис структури параметрів у методі saleOrderCreate для створення ТТН Нової Пошти

20 Sept 2023, 16:59 UTC296 viewsread 9 August 2026

Додані нові поля у методі saleOrderCreate, а саме: - contract - contact - rate - discountPercent - supplyDate - reserveDate - payBefore - taxAccount - userPresentation

8 May 2023, 16:06 UTC314 viewsread 9 August 2026

Додано можливість ідентифікації по артикулу товару у методі saleOrderCreate

25 Apr 2023, 13:43 UTC300 viewsread 9 August 2026

Додано можливість вказати limit та offset в методі request. Детальніше

25 Apr 2023, 11:14 UTC281 viewsread 9 August 2026

saleOrderCreate: можливість ідентифікації товарів по артикулу

25 Apr 2023, 11:05 UTC272 viewsread 9 August 2026

Документація API Dilovod https://dilovod.crisp.help/uk/article/api-dilovod-1gwt3m0/#2-saleordercreate-stvorennya-zamovlennya-pokupcya

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

“Dilovod API” (@dilovodapi), 76 subscribers as measured 23 August 2026. Telegram Register, tgregister.com/channel/dilovodapi.

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.