Discord HTTP API (Preview)

Name: Discord HTTP API (Preview) API
Brand: Discord HTTP API (Preview)
Availability: InStock

✓ Official Vendor SpecCommunicationsChat MessagingapiKey, oauth2217 EndpointsREST

For Agents

Send and manage messages, channels, members, roles, and application commands across Discord servers. Useful for community moderation, gaming, and chat-automation agents.

Quickstart

Get started with Discord HTTP API (Preview) in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"send a message to a Discord channel"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Discord HTTP API (Preview) API.

Manage guilds, channels, and threads — create channels, archive threads, edit topics

Send, edit, and delete messages, embeds, and reactions across channels via /channels/{channel.id}/messages

Manage guild members, roles, and permissions including bans, timeouts, and role assignments

GET STARTED

Start building with Discord HTTP API (Preview) API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Discord HTTP API (Preview) API for, with concrete tasks.

★ Community Moderation Bots

Discord bots can automate moderation across busy guilds by listening for messages, applying timeouts, removing bad actors, and logging actions. The HTTP API provides direct access to message management, member bans, role assignment, and audit log retrieval. Combined with the Gateway for real-time events, bots can react to thousands of messages per minute and keep large communities healthy without hiring round-the-clock human moderators.

On a flagged message in channel ID 12345, call PUT /guilds/{guild.id}/members/{user.id} to apply a 1-hour communication timeout and DELETE /channels/{channel.id}/messages/{message.id} to remove the message.

Slash-Command Driven Game and Productivity Apps

Developers can ship slash commands that let users trigger game actions, run polls, fetch stats, or call internal APIs from within Discord. Application commands are registered via /applications/{application.id}/commands and respond through the interactions endpoint. This delivers a no-install user experience: members run commands directly inside the chat where they already collaborate.

Register a /stats slash command via POST /applications/{application.id}/commands, then handle the interaction by replying with the user's ranked-match win rate.

Webhook Notifications from External Systems

Engineering teams can pipe alerts from monitoring, CI, and product systems into Discord channels using webhooks. Webhooks accept rich embeds with color-coded statuses, fields, and links, making them well suited for incident channels and release announcements. No bot user is required, and webhook URLs can be scoped per channel for clean separation.

POST a JSON payload with an embed describing a deployment failure to /webhooks/{webhook.id}/{webhook.token} for the #incidents channel.

Community Analytics and Member Insights

Community managers can pull membership lists, role distributions, and channel activity via /guilds/{guild.id}/members and related endpoints to build dashboards on engagement and retention. Joined with audit log data, these analytics inform programming decisions like which channels to feature or sunset. Discord's API limits and pagination guide ETL frequency, but daily snapshots are common.

List guild members via /guilds/{guild.id}/members with pagination and aggregate counts by role into a daily community-health snapshot.

AI Agent for Discord Server Management

AI agents can run as Discord-server copilots — answering questions, creating channels, registering slash commands, and posting summaries — by calling the Discord API through Jentic. Bot tokens are stored in MAXsystem and never reach the agent's context. Searching Jentic for 'send a Discord message' returns the right operation directly, removing the need to navigate Discord's lengthy reference docs.

Search Jentic for 'send a Discord message', load the schema for POST /channels/{channel.id}/messages, and execute it with content and an embed for the daily community digest.

Key Endpoints

217 endpoints — the discord http api powers bots, integrations, and applications across discord servers (guilds), channels, voice connections, and user accounts.

METHOD

PATH

DESCRIPTION

POST

/channels/{channel.id}/messages

Send a message to a channel

GET

/users/@me/guilds

List guilds the current user is a member of

POST

/users/@me/channels

Create a DM channel with another user

GET

/oauth2/userinfo

OAuth2 user info for the current token

GET

/gateway/bot

Get the WebSocket gateway URL and shard recommendation for bots

GET

/voice/regions

List available voice regions

GET

/oauth2/@me

Get current authorization information

POST

/channels/{channel.id}/messages

Send a message to a channel

GET

/users/@me/guilds

List guilds the current user is a member of

POST

/users/@me/channels

Create a DM channel with another user

GET

/oauth2/userinfo

OAuth2 user info for the current token

GET

/gateway/bot

Get the WebSocket gateway URL and shard recommendation for bots

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Discord bot tokens and OAuth2 client secrets are stored encrypted in Jentic's MAXsystem vault. Agents call channels/guilds/oauth2 operations through scoped Jentic sessions; the raw 'Bot <token>' header value never enters the agent's context window.

Intent-based discovery

Agents search by intent (e.g., 'send a Discord message' or 'register a slash command') and Jentic returns the matching Discord operation across the 217-endpoint surface, so the agent can pick the right route without browsing the Discord developer reference.

Time to first call

Direct Discord integration: 1-2 days for app registration, OAuth scopes, intents config, rate-limit handling, and webhook signing. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Slack

Workplace messaging and collaboration platform

Choose Slack for B2B workplaces and enterprise integration; choose Discord for community, gaming, and creator-led servers.

Alternative

Mattermost

Self-hosted open-source team messaging

Choose Mattermost when you need self-hosted control; choose Discord for hosted, large-scale community workloads.

Complementary

Twilio

Multi-channel SMS, voice, and chat APIs

Use Twilio for SMS/voice notifications outside Discord; use Discord for in-server chat and community management.

Complementary

SendGrid (API Keys)

Transactional email delivery

Pair SendGrid email notifications with Discord chat alerts to reach members across both channels.

FAQs

Specific to using Discord HTTP API (Preview) API through Jentic.

What authentication does the Discord HTTP API use?

Discord supports two schemes: a bot token sent in the Authorization header as 'Bot <token>' for bot identities, and OAuth2 bearer tokens for user-context calls and app installation. Through Jentic, both bot tokens and OAuth client secrets are held in the MAXsystem vault, and the agent receives only scoped sessions to call /channels, /guilds, and /oauth2 endpoints.

Can I send a message to a channel with the Discord HTTP API?

Yes, POST /channels/{channel.id}/messages accepts content, embeds, components (buttons, selects), allowed_mentions, attachments, and message references for replies. The bot or webhook posting must have access to the channel and the Send Messages permission.

What are the rate limits for the Discord HTTP API?

Discord enforces per-route, per-resource, and global bucket-based rate limits, communicated through X-RateLimit-* headers and a global cap of around 50 requests per second per bot. 429 responses include a retry_after value. Honour the headers on each request — Discord aggressively bans bots that ignore rate limit responses.

How do I register a slash command for a Discord application through Jentic?

Search Jentic for 'register Discord slash command', load the POST /applications/{application.id}/commands operation, and execute it with the application ID and the command definition (name, description, options). For guild-scoped commands, use /applications/{application.id}/guilds/{guild.id}/commands.

Is the Discord HTTP API free?

Yes, the Discord HTTP API is free for bots and applications, subject to Discord's Developer Terms of Service and rate limits. Some features (such as activity insights and verified bot status) require additional approval, and large bot operators must apply for verification once they reach 75 servers.

Can I retrieve a guild's members and roles with the Discord HTTP API?

Yes, GET /guilds/{guild.id}/members lists members (with pagination via the after parameter and a limit up to 1000) and GET /guilds/{guild.id}/roles returns the role definitions. The bot must have the Server Members Intent enabled and be authorised in the guild to read full member data.