Bots — the new interface
for Bitrix24

Build bots in minutes, not days. Migrate from Telegram with a single prompt. 33 endpoints for total control — from registration to reactions.

Bot = interface

Instead of pages — a conversation. Instead of buttons — commands. Instead of forms — messages. The bot lives where your team already works — right in Bitrix24 chat.

Bot = interface

No need to teach people a new interface. They already know how to type in chat. A bot is an app you don't have to open separately.

  • Lives in chat — no tab switching
  • Buttons and keyboards instead of forms
  • Notifications straight into the work chat
  • AI models built in — the bot thinks for itself

Everything you need to build bots

A full API stack: from bot registration to inline keyboards and server infrastructure

33 API endpoints

A full imbot.v2 wrapper: registration, messages, commands, chats, files, reactions. All through a single REST API with your key

Registration in one call

POST /v1/bots/register — and the bot is already in chat. No OAuth dances, no marketplace submissions. Code, name, type — done

Buttons and keyboards

Inline buttons, keyboards, message reactions. Bots can be interactive — like a mini-app right inside chat

Events without webhooks

Events via polling — perfect for servers without a public IP. Works behind NAT, inside Docker, from Black Hole. No SSL certificates required

Migration from Telegram

Hand AI your old Telegram code plus the Vibe Bot API docs — get a ready Bitrix24 bot. The API is designed to make migration trivial

Managed Bots

Server plus a registered bot out of the box. Create a bot — get a cloud VPS, an API key, and a prompt for the AI model. All you have to do is write the code

A bot in a single prompt

Don't write code by hand. Describe your bot in Claude or Cursor — copy the prompt, paste into AI, get working code.

Prompt: Echo bot

Create a bot for Bitrix24 in Node.js using the VibeCode Bot API.

API: https://vibecode.bitrix24.com/v1
Docs: https://vibecode.bitrix24.com/docs/bots
Auth: X-Api-Key header

The bot should:
1. Register via POST /v1/bots/register (code, name, type: 'B')
2. Receive events via POST /v1/bots/events/poll (long-polling)
3. Reply to every message via POST /v1/bots/messages/send

The API key is passed via the VIBE_API_KEY environment variable.

Telegram → Bitrix24: what changes

The API is built on the same principles. If you've built Telegram bots before — everything will feel familiar.

Already have a Telegram bot?
Convert it in 2 minutes

Hand AI your existing Telegram bot code along with the VibeCode docs link — get a ready Bitrix24 bot.

1
Copy the prompt
Copy the prompt
Paste your Telegram bot code and the link to the VibeCode Bot API docs
2
Send it to AI
Send it to AI
Claude, Cursor, or ChatGPT converts every Telegram API call into Vibe Bot API
3
Run it
Run it
The bot runs in Bitrix24 chat. Polling, keyboards, commands — all in place

Frequently asked questions about bots

Everything about the VibeCode bot platform

Can I migrate a bot from Telegram to Bitrix24?

Yes. The VibeCode Bot API is designed by analogy with the Telegram Bot API. Copy your bot code and a prompt with the docs into an AI model — it will automatically convert Telegram API calls into Vibe Bot API.

How many endpoints does the Bot API have?

33 endpoints: bot registration and management, sending messages, keyboards, reactions, files, events, commands. Full control over your bot via REST API.

Do I need a server to run a bot?

For polling bots — yes, you need a process that polls the API. You can use the free Black Hole server from VibeCode or your own server.

Does the Bot API support inline keyboards?

Yes. Both regular and inline keyboards are supported, along with buttons with callback data, dialog windows, and context menus. All via JSON in the message parameters.

Ready to build a bot?

Get an API key, copy the prompt into AI — and your bot is ready. From idea to working bot in 5 minutes, without writing code by hand.