Bring your bots. The developer portal is open.
A Discord-compatible bot API: REST plus a real-time gateway, slash commands, embeds and webhooks. Create an application at developers.voidcom.app and point an existing discord.js or discord.py bot at Voidcom by changing its base URL.
Discord-compatible by design
The developer portal is live at developers.voidcom.app. Sign in with your Voidcom account, create an application and copy its bot token; it is shown once. A server admin then adds the bot from the application's install link. The API is a documented subset of Discord's API v10: the same REST paths under /api/v10, the same gateway opcodes and JSON shapes, Bot token auth and Discord's rate-limit headers, so an existing discord.js or discord.py bot connects by changing its base URL.
- REST routes under
/api/v10, shaped like Discord's; anything outside the subset answers501 - Bot-token auth with the
Authorization: Bot <token>header; rotate the token from the portal at any time - discord.js: set
rest.apitohttps://api.voidcom.app/api. discord.py: setdiscord.http.Route.BASE - voidcom.py and voidcom.js, thin forks with the Voidcom defaults built in, follow once they are published
REST + real-time gateway
Read and write messages, channels, servers, members, roles and bans over REST. Events arrive over a WebSocket gateway that speaks Discord's opcodes: HELLO, IDENTIFY, READY, HEARTBEAT, DISPATCH and RESUME, which replays the frames a dropped connection missed. Dispatch is filtered by the intents you declare, and every response carries per-route rate-limit headers, so the libraries pace themselves the way they do on Discord.
- Message, channel, guild, member, role, ban, invite and audit-log endpoints
- Reactions, pins, typing, embeds and message components (buttons, string selects)
- Gateway with heartbeats, RESUME and intent-gated dispatch
Slash commands & webhooks
Register global and per-server slash commands, receive interactions over the gateway and answer them with messages, deferred responses, ephemeral replies or edits. Create webhooks for outbound messages and pipe GitHub and Slack events straight into a channel with the built-in ingest adapters.
- Global and guild-scoped slash commands, bulk overwrite as on Discord
- Interactions arrive over the gateway; buttons and string selects fire back as component interactions
- Webhook create and execute, plus GitHub and Slack ingest
What is not there yet
The Voidcom apps do not render embeds or components and have no slash-command picker yet. Until the next client release, a bot's embeds appear as plain messages and its slash commands cannot be invoked from the apps. Bots are text only; there is no voice for bots. There is no OAuth2 authorize URL; the install link from the portal replaces it. Bots never see the content of end-to-end encrypted direct messages and cannot post into them. The complete list is on the differences page.
- No embed or component rendering and no slash-command picker in the apps yet
- No voice for bots, no OAuth2, no access to encrypted DMs
- The bot API runs as its own service with health probes, separate from the core server