What is a bot for MAX messenger?
MAX is a messenger with a partner platform for business: chat bots, mini-apps, channels and a Digital ID service. A bot there is a program that receives events from users over an HTTPS API and answers with messages, buttons and files. The docs describe typical uses: auto-replies, help scenarios and order handling.
You can build a bot three ways. No-code constructors from partner services use ready templates. The official Bot API suits custom logic, and the docs link official JavaScript and Go libraries plus an OpenAPI schema. For anything that touches your database, payments or CRM, the API route is the realistic one.
Mini-apps are a separate product: web apps in HTML, JavaScript and CSS that talk to the MAX client through the MAX Bridge library. A bot and a mini-app often work together, the same way a Telegram bot works with a Telegram Mini App.
Who can publish a bot and what the platform requires
This is the main difference from Telegram, where anyone can create a bot in a minute. In MAX you first connect to the platform. Per the docs, it is open to legal entities, sole proprietors (IP) and self-employed people who are Russian residents. Individuals who are not self-employed and non-residents cannot pass verification yet.
Verification goes through Gosuslugi or a bank ID, and the person confirming must be the head or an administrator, not an ordinary employee. Only after that you pick the bot service and create a bot. The number of bots per profile depends on the profile type, so check the current limit in your account.
- Create a profile (organization, IP or self-employed) in the "MAX для бизнеса" mini-app or on the web platform.
- Verify it through Gosuslugi or a bank ID.
- In the Chat bots section fill in the card: logo, name and description. Check the current size and length requirements in the platform docs.
- The nickname rules are set by the platform; check them before you print it anywhere.
- The bot goes to moderation; review takes time, so plan for it before a launch date; the status is shown next to the bot name.
- After publication the bot is searchable by nickname. Editing a published bot sends it back to moderation.
MAX bot vs Telegram bot: what is actually different
The idea is the same: a token, an HTTP API, updates in, messages out. The differences are in rules and details, and they affect the plan more than the code does.
Access is the biggest one. A Telegram bot needs no company behind it. A MAX bot needs a verified Russian profile and passes moderation, and editing the card repeats it. Plan for that before you promise a launch date to the business.
- Who can publish: Telegram, anyone. MAX, verified Russian organizations, IP and self-employed.
- Moderation: Telegram has none for a regular bot. MAX reviews the card before publishing.
- Production transport: Telegram allows webhook or long polling. MAX docs recommend webhook everywhere and call long polling a development tool.
- Webhook: MAX accepts only HTTPS on port 443 and no self-signed certificates. Telegram allows a self-signed certificate if you upload it.
- Message text: up to 4000 characters in MAX; Telegram's limit is 4096.
- Buttons: MAX inline keyboards have callback, link, open_app, request_geo_location, request_contact, message and clipboard buttons, with up to 7 buttons per row and 30 rows.
How the Bot API delivers updates: webhook and long polling
The API lives at platform-api2.max.ru and the token goes in the Authorization header; passing it in the query string is no longer supported. The API has a request limit and answers 429 when you exceed it, so send through a queue with a rate limiter. Updates arrive in two ways, and you cannot use both at once.
Long polling is GET /updates. The docs say it is limited in speed and in how long events are stored, and that it is meant for development and testing only. In production use a webhook: POST /subscriptions with an HTTPS URL, an optional list of update types and an optional secret. MAX sends the secret back in the X-Max-Bot-Api-Secret header, and you should reject requests where it does not match.
Delivery rules matter for design. Your endpoint must answer 200 within 30 seconds. Failures are retried up to 10 times with growing intervals, and after 8 hours without a success the bot is unsubscribed. So do the real work in a queue: acknowledge the update, store it, process it in a worker. The same logic as in our comparison of Telegram webhook and long polling applies, and so does webhook signature checking.
What you can reuse from a Telegram bot
If the Telegram bot is written well, most of it is not about Telegram. Business rules, database, CRM and payment integrations, notifications and admin tools sit behind an interface. Only the thin edge that parses incoming updates and calls the send API is channel-specific.
That is the channel adapter pattern. An adapter converts a native update into an internal event (user, text, button press, attachment) and converts an internal reply back into a native call. The core never imports a Telegram or MAX client. Adding MAX then means writing one adapter, one webhook handler and a mapping of identities, not a second bot.
- Reusable as is: scenarios and state, CRM and 1C integrations, payments logic, background jobs, admin panel, analytics.
- Needs an adapter: incoming update parsing, outgoing messages, keyboards, file upload, command registration.
- Needs a decision per channel: markup format, button limits, what to do when one feature exists in only one messenger.
- Must be stored per channel: external user id, chat id, consent and opt-out status.
How to run two channels without duplicating logic
Keep one user record with several channel identities, and one conversation state independent of the messenger. Our notes on conversation state in bots apply directly: the state machine should be keyed by an internal user id, not by a Telegram chat id.
Make handlers idempotent. Both platforms retry undelivered webhooks, so the same update can arrive twice. Store the update id or a hash and skip repeats, as described in API idempotency and retries. Send outgoing messages through a queue with a per-channel rate limiter, since the limits differ.
Write tests against the internal event, not against raw payloads. Then a new channel needs only adapter tests. Keep the feature gap explicit: if a scenario depends on a feature that exists in one messenger only, define the fallback instead of discovering it in production.
When you do not need a MAX bot
Do not build one just because the channel exists. If your audience is outside Russia, or your customers do not use MAX, the work has no payoff. The platform is limited to Russian residents on the business side, so a foreign company cannot publish a bot there at present.
You also do not need custom development if a no-code constructor covers the scenario: a simple FAQ, a menu, a lead form. Start with a template, and move to code when you need your own database, complex state or integrations. And if you cannot yet say how many of your customers are in MAX, ask them or measure a pilot first; the official docs we reviewed give no audience figures.
When a contractor makes sense
A contractor helps when the bot is part of a system: it reads orders from a CRM, writes payments, handles queues and must keep working during deploys. It also helps when you already have a Telegram bot and want a second channel without a rewrite, since the work is refactoring toward adapters.
What you still do yourself: the profile, verification and ownership of the account. The bot belongs to your organization on the platform, so keep the access and the token with you, and give the developer only what the integration needs. See our Telegram and messenger bot development page for how we approach it, and the cost factors of a bot for what drives the budget.