Your first 15 minutes

Status Stable · Last verified 2026-07-11 · API v10 · Source Quick start

The single best way to learn this platform is to make a message appear in a channel you control. We’ll do that with a webhook first (zero setup), then point you at the learning path.

Prerequisites

• A Discord account and a server (guild) where you have Manage Webhooks / Manage Server permission. Free to create: click the + in the server list → Create My Own.
• Node.js ≥ 20 if you want to run the example (node --version).

Step 1 — Post to a channel in 3 minutes (webhook)

Follow Get a DISCORD_WEBHOOK_URL to copy a webhook URL, then:

git clone https://github.com/snowyukitty/discord-platform-atlas
cd discord-platform-atlas/examples/webhook-minimal
cp .env.example .env         # paste your webhook URL into .env
node send.mjs

You should see a message and an embed appear in the channel. If not, the example README lists the common errors (401/404 = bad URL, 429 = rate limited).

That is a complete, real integration — no bot, no token, no server.

Step 2 — Decide where you’re going

Read Choose an integration model. Most people land on one of:

• “I only push notifications” → you’re already done; deepen with sending messages (embeds, threads, rate limits).
• “Users will run commands” → Interactions, then the interaction-endpoint example (serverless-friendly, no socket).
• “I need to react to live events” → Apps & Bots and the Gateway, then the bot-gateway-minimal example.

The learning path

A suggested progression from beginner to advanced. Each rung is independently useful — stop wherever your project needs.

Beginner

1. Platform overview — the mental model.
2. Webhooks — post-only messaging; embeds and formatting.
3. Security basics — how to hold a secret without leaking it.

Intermediate 4. Apps & Bots — create an app; understand tokens vs IDs vs keys. 5. Interactions — slash/user/message commands; buttons, selects, modals. 6. Gateway & intents — real-time events; privileged intents and their limits. 7. OAuth2 & installation — scopes; user-install vs guild-install.

Advanced 8. Components V2, modals, and follow-up messages — see Interactions. 9. Rate limits, sharding, and caching — see the platform map and the research backlog. 10. Monetization, Activities, and emerging features — tracked in the platform map and changelog watch.

A note on scopes and least privilege

When you do create an app, resist the urge to grant everything. Request the narrowest OAuth2 scopes and intents that make your feature work. It is easier to add a permission later than to explain to users why your bot asked for Administrator. See Security.