Features Technology Parity Pricing Docs
Gaming & eSports
Privacy
Communities
Blog Download
Live

Bring your bots. Change one line.

A Discord-compatible bot API — REST plus a real-time gateway, slash commands, and webhooks. Most existing discord.js bots run by pointing them at Voidcom.

Discord-compatible by design

The bot API mirrors Discord's REST routes and gateway opcodes, so the libraries you already know work against Voidcom. With discord.js, you change the API host and gateway URL and log in with a Voidcom bot token — no rewrite.

  • REST routes mounted under /api/v10, shaped like Discord's
  • Bot-token auth with the Authorization: Bot <token> header
  • discord.js connects by overriding the REST and gateway URLs
  • discord.py works behind a small host-rewrite proxy or a fork that accepts a custom API URL
discord.js REST /api/v10 Bot Tokens Intents

REST + real-time gateway

Read and write messages, channels, servers, members, roles, and bans over REST. Receive events in real time over a WebSocket gateway that speaks Discord-style opcodes — HELLO, IDENTIFY, READY, HEARTBEAT, RESUME, and DISPATCH.

  • Message, channel, guild, member, role, and ban endpoints
  • Reactions, pins, and typing
  • Gateway with heartbeat, resume, and intent-gated event dispatch
WebSocket Gateway Heartbeat / Resume Event Dispatch

Slash commands & webhooks

Register global and per-server slash commands and respond to interactions. 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
  • Interaction callbacks with Ed25519-verified delivery
  • Webhook create / execute, plus GitHub and Slack ingest
Slash Commands Interactions GitHub Ingest Slack Ingest

Encryption-aware, independently deployed

The bot API runs as its own service, so it scales independently from the core server. Bots that want to send into encrypted channels can fetch a user's public key to participate in Voidcom's hybrid post-quantum encryption.

  • Standalone service with its own container and health probes
  • Public-key endpoint for E2E-aware bots
  • Voice is not yet exposed to bots — it's on the roadmap
Standalone Service E2E-Aware Scales Independently