Update Dump: Raw JSON of Messages

Writing a bot and wondering why your handler never fires? Chances are you expect one field and Telegram sends another. Update Dump answers that in seconds: you send a message and get its JSON update back.

The bot is meant for people who need to see data the way code sees it. There is a single command, /start, and after that you simply write to it. ✨

What the JSON contains

When a user messages a bot, Telegram builds an Update object. Inside sits the message itself: its identifier, sender, chat, date, and the text or attachment. Those same objects arrive in the handlers of your own bots.

Update Dump returns that update in readable form. You do not need to run a server, write code or plug in a token just to peek at the structure.

Where it helps in practice

• Finding ids. The id of a chat, a user or a forwarded message is needed for mailings and access rules.
• Identifying content type. Photo, sticker, voice note, document, poll: each has its own fields and nesting.
• Checking formatting. The entities field shows where a message has bold text, links and mentions.
• Decoding forwards. The JSON shows where a forwarded message came from, if the sender allowed it.

Writing a parser gets easier: look at a real sample first, then write the field access.

Send, copy, compare

1. Open the bot and press /start.
2. Send the message whose structure you want to see: text, photo, voice, sticker.
3. Copy the JSON from the reply into your editor and find the fields you need.

To compare, send several kinds of content one after another. Differences in structure jump out at once.

How updates work in the Bot API

Bots receive updates in two ways: the getUpdates method or a webhook. The two cannot run at the same time. Either way you get Update objects serialized as JSON.

The server keeps unprocessed updates for no more than 24 hours. If your bot stays silent for long, old events disappear. For reliable operation your code should collect updates without long gaps.

Privacy and caution

The JSON often shows your name, username and numeric id. Do not send the bot messages that contain passwords, codes, payment details or other people's personal information. Neutral test text is enough.

If you are studying a message from a work chat, strip ids and names before you post the JSON on a forum or in a bug tracker. They are personal data just like a phone number. ⚠️

As with any public bot, there are no guarantees about storage or uptime. For critical debugging, a private test bot with logging is the wiser choice. 🔍

Who needs it

The bot suits beginner and experienced developers, automation builders and the plain curious. It does one thing well: it shows data honestly, without decoration. The author is named in the bot profile if you need to reach them.