# Webhooks and your users' data

> The events your bot sends to your systems, and what happens to the projects and history of the people who use it.

## Webhooks for the bot

Subscribe a [webhook destination](https://developer.vidmoat.com/developer/webhooks) to these events. They are signed exactly like render events; see [verifying webhooks](https://developer.vidmoat.com/developer/docs/webhooks).

| Event | When |
| --- | --- |
| `credits.low` | Your balance fell below 200 while the bot worked (at most daily). |
| `credits.exhausted` | The bot refused work because your balance was short (at most every 6 hours). |
| `app.suspended` | We suspended the app; its keys and bot stop. |
| `telegram.end_user.limit_reached` | Someone hit your per-person daily cap (once per person per day). |
| `telegram.end_user.first_seen` | Someone used the bot for the first time (once per person). |
| `telegram.end_user.blocked` | You blocked someone, in the console or with the API (once per block). |

## Your users' data

Each person gets an account that belongs to your app and to nothing else: their projects are invisible to other people using your bot, to other apps, and to your own editor. You see who used the bot and what it cost, not their footage, and you can delete one person's projects and history from the Telegram tab. Deleting the app deletes all of them. What they spent stays on your ledger.

---

Source: https://developer.vidmoat.com/developer/docs/telegram/webhooks-and-data
Previous: [Supporting your users](https://developer.vidmoat.com/developer/docs/telegram/support.md)
Next: [MCP server](https://developer.vidmoat.com/developer/docs/mcp.md)
All documentation: https://developer.vidmoat.com/llms-full.txt