What it does
The Discord Developer Platform provides APIs and developer tools for apps that run inside Discord or connect games to Discord features. Bots and companion apps can use HTTP endpoints, Gateway events, OAuth2, slash commands, and interaction callbacks. The official first-bot guide shows a JavaScript app that registers commands, exposes a public interaction endpoint, and responds to user actions. It is the service developers build against, not an API client for calling unrelated services.
Build an interaction before a full bot
Discord's first-bot tutorial begins by creating an app in the Developer Portal, retrieving its application ID and public key, and generating a bot token. It then configures installation contexts and permissions, registers a slash command through the HTTP API, and exposes a public endpoint that verifies and handles Discord interactions. The guide uses JavaScript and an Express server, but the platform also documents other integrations and game-oriented features.
A practical first version might accept a slash command such as /status and return a short response. The application must be reachable at the configured interaction endpoint, and its token must be kept private. Apps that need events beyond interactions can use the Gateway API, subject to the appropriate intents and permissions.
Rate limits are an important design constraint, not an optional optimization. Discord says limits can vary by route and account, advises clients to inspect response headers rather than hard-code route limits, and returns a retry delay with HTTP 429 responses. Invalid requests can also cause temporary restrictions. The official pages reviewed here do not establish a standalone price schedule for using the developer platform, so this entry makes no pricing claim.
Strengths
- The platform combines HTTP endpoints, Gateway events, slash commands, interactions, OAuth2, and game-related integration features.
- The first-bot guide follows a concrete path from app registration to command registration and interaction handling.
- Rate-limit documentation explains response headers and retry behavior for handling 429 responses.
Watch out for
- A deployed interaction app needs a public endpoint and carefully managed application credentials.
- Per-route and global limits can vary, so applications must handle rate-limit responses instead of assuming fixed quotas.
Best for
- Creating a Discord bot that responds to slash commands and interactions
- Integrating a game with Discord presence, voice, or social features
- Automating Discord server workflows through authenticated API requests
Sources
- Discord Developer Platform - Documentation - Discord (Oct 25, 2026)
- Building your first Discord Bot - Documentation - Discord (Oct 25, 2026)
- Rate Limits - Documentation - Discord (Oct 25, 2026)