Upload and manage emojis owned by a Discord application (bot) rather than by a specific guild
domain: docs.discord.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
POST /applications/{application.id}/emojis with a name and base64 image data URI to create an application-owned emoji
Keep uploads within the 256 KiB file-size limit and the 128x128 recommended image dimensions for the emoji
Use GET /applications/{application.id}/emojis to list the application's emojis, or GET the single-emoji endpoint by ID
Reference application emojis in messages the same way as guild emojis; the USE_EXTERNAL_EMOJIS permission is not required for the bot to use its own app emojis
Use PATCH/DELETE on /applications/{application.id}/emojis/{emoji.id} to rename or remove an application emoji
Known gotchas
An application can own at most 2000 emojis total — far more than a single guild's normal emoji slots, but still a hard ceiling worth tracking if a bot generates emojis dynamically
Emoji management routes don't follow Discord's normal rate-limit conventions; they're throttled per-guild specifically to prevent abuse, so returned rate-limit headers may not accurately reflect your remaining quota
Uploading an oversized emoji fails with a 400 Bad Request that is not a normal Discord JSON status code, so error-handling code built around standard JSON error codes needs a special case for this endpoint
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?