GROM Bot APIBuild bots for GROM

Before you start ​

This platform is under construction. The Bot API gateway is not deployed — every method documented here returns 404 today, and there is no way to obtain a bot token yet.

That is not a caveat buried in a footnote; it is the single most important fact on this site. The reference is published early so the design can be reviewed and migrations planned, and every page is marked accordingly. Implementation status lists what runs, what does not, and gives you the commands to check for yourself rather than trusting this page.

What a bot is ​

A bot is an account your program controls. It has a username, it appears in chats, and it acts through this HTTP API instead of a phone. It cannot start a conversation — someone has to message it or add it to a group first. That restriction is the platform's main defence against bots being used for spam, and there is no way around it.

Three things a bot does well:

Answer. Someone sends /weather Tashkent, your program replies. This is most bots, and it needs one method: sendMessage.

Announce. Your build finishes, your program posts to a channel. No user interaction at all — the bot is an output device.

Host. A Mini App opens inside the chat, with your web app running in a webview and a bridge back to the platform.

The shape of a request ​

Every method lives under your token and takes JSON:

curl https://api.casinoplaneta.info/bot$TOKEN/sendMessage \
  -H 'Content-Type: application/json' \
  -d '{"chat_id": 1337, "text": "Salom!"}'

Every response carries ok:

{ "ok": true, "result": { "message_id": 42, "date": 1770000000 } }

{ "ok": false, "error_code": 403, "description": "Forbidden: bot was blocked by the user" }

Branch on ok before touching result. Most failures are permanent — a blocked bot stays blocked — so retrying blindly wastes your rate limit and never succeeds. Errors covers which ones are worth a second attempt.

Where to go next ​