Changelog

Changes to the developer platform, newest first. The App API is versioned (v1); within a version, things are only added.

2026-11-04

Phase 2: bots that do things.

• Messages: read, send, edit, delete, reply, react, pin, typing, with embeds and components (buttons and select menus), allowed_mentions, nonce and game cards. See Message.
• Servers: channels, roles, members (nickname, timeout, roles, kick), bans, invites. See Server and Channel.
• Intents: SERVER_MEMBERS, PRESENCE and MESSAGE_CONTENT, turned on per application on the Bot tab. See Intents.
• Commands and interactions: slash commands and context-menu commands with options, autocomplete and default permissions; interactions delivered to a signed HTTPS endpoint (Ed25519) with ephemeral and deferred answers, followups, buttons, menus and modals. See Interactions and Components.
• Rate limits in Discord's scheme with X-RateLimit-* headers. See Rate limits.
• Developer Portal: new Interactions tab (address, verification, public key, new key) and Commands tab; Intents on the Bot tab.
• The App API now runs in its own process, apart from the main API: a flood of bot calls or a restart of either cannot take the other down.
• GET /applications/@me now says bot_user_id (it was botUserId) and lists the application's intents.
• This wiki was rebuilt after Discord's developer documentation: sections for guides, developers, reference and change log, a page per resource, and an outline on every page.
• Examples: every call in the reference and the guides now has a request card with tabs (curl, JavaScript, Python) and a response card with its status. The samples show what the API really sends: a field that has no value is left out, never null.

2026-11-03

Phase 1 released.

• Applications with draft and published states, branding, Czech translations, testers and an audit log, in the Developer Portal (developer.moymo.net).
• Bots: create, username, picture, token (shown once, reset at will), delete. A bot is a member with a BOT tag that cannot sign in.
• Adding a bot to a server with the bot scope: a server picker, permissions as checkboxes, a managed role just below the person who added it.
• Domain verification with a TXT record at _moymo-app.<domain>.
• OAuth2: authorization code with PKCE (S256), client secrets, refresh tokens used once, revoke; consent page at moymo.net/oauth2/authorize; Settings > Connected apps.
• Scopes: identify, email, servers, bot (others named and planned).
• App API v1 at https://moymo.net/api/app/v1: GET /users/@me, GET /users/@me/servers, GET /applications/@me.
• Developer mode in the Servers add-on 1.17: Copy ID for servers, channels, categories, messages, members, posts, roles and emoji.
• The names developer, wiki, docs, portal, bots, gateway, sdk, oauth and similar are reserved and cannot be profile addresses or usernames.
• BOT tag: every bot wears a BOT tag beside its name in the Servers add-on (1.18).
• Review and suspension: staff can approve or turn down an application that asked for the App Directory, and suspend one that is being abused; a suspension stops every credential of it on the next request.
• This wiki.