API versions & verification metadata

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

How Discord versions the API

• The version is in the URL path: https://discord.com/api/v10/....
• The gateway is versioned via a query parameter (?v=10&encoding=json).
• Older versions are marked deprecated or discontinued; unversioned requests default to an old version and should not be relied on.
• v10 is the current major used throughout this atlas. New features (polls, Components V2, user-installs, monetization refinements) ship on top of v10 rather than forcing a new major.

Why we pin a version

Every code sample and endpoint here targets v10 explicitly. Pinning means a future default-version bump won’t silently change behavior under you. If you see a sample without a version, treat it as a bug to fix.

Verification metadata on every page

Each content page’s frontmatter carries:

status: Stable          # confidence label (see /reference/feature-status/)
lastVerified: 2026-07-11 # ISO date claims were last checked
apiVersion: v10          # the API major the page targets
sources:                 # primary/authoritative URLs
  - https://docs.discord.com/developers/...

and a matching one-line banner at the top of the body, so both the website and raw-Markdown (GitHub) readers see it.

Keeping it current

• The changelog watch tracks Discord-side changes we should reflect.
• When you update a page, bump lastVerified and re-check the linked sources.
• Structural facts (how versioning works) change rarely; numeric limits and availability change more often — re-verify those first.

Documentation host note

[!TIP] Observation Discord’s developer docs are served from docs.discord.com/developers/...; older discord.com/developers/docs/... links generally still resolve. We link to docs.discord.com as canonical. Last checked 2026-07-11.