Voidcom for developers
Applications

Documentation

Voidcom bot platform

Voidcom speaks a documented subset of the Discord bot API: the same REST paths under /api/v10, the same gateway opcodes and JSON shapes, Bot token auth and Discord's rate-limit headers. A Discord bot moves over by changing its base URLs. Bots are text only in v1 — no voice — and anything outside the subset answers 501.

Start here

  • Getting started Create an application, copy its bot token, add the bot to a server and run a first bot against the Voidcom API.
  • Authentication & applications What an application is, how the bot token works, rotation, gateway intents, the install link and the fields the portal stores for later.
  • Migrate a Discord bot in 10 minutes The checklist for pointing an existing discord.js or discord.py bot at Voidcom, and what to expect to break.

Reference

  • Gateway Connecting to the gateway, HELLO / IDENTIFY / READY, heartbeats and zombie detection, RESUME, Invalid Session, close codes, and the events each intent delivers.
  • Interactions Registering slash commands, the INTERACTION_CREATE payload, callback types, the original response and follow-ups, ephemeral replies, buttons and select menus, embed limits and the error codes.
  • Rate limits The global limit, per-route buckets, the response headers and the 429 body — Discord's shape, so library back-off works unchanged.
  • API reference Every REST operation with schemas, voidcom.py / voidcom.js / curl samples and try-it — generated from the server.
  • Differences from Discord Everything that behaves differently from Discord or is not in the Voidcom subset — ids, voice, encrypted DMs, permissions, intents, installation, interactions, gateway details — with a machine-readable list.