Feature-status labels
このコンテンツはまだ日本語訳がありません。
Status
Stable· Last verified 2026-07-11 · APIv10
Every page carries a status so you know how much to trust and build on it. These are our labels for our confidence, informed by Discord’s own availability signals.
| Label | Meaning | Build on it? |
|---|---|---|
Stable |
Documented, generally available, unlikely to change without notice. | Yes. |
Limited |
GA but gated: allowlist, app review, size threshold, region, or platform. | Yes, if you qualify — note the gate. |
Experimental |
Officially in preview/beta; may change or be withdrawn. | Prototype only; pin versions; expect churn. |
Deprecated |
Still works but officially discouraged; may sunset. | Migrate away; note the sunset date if known. |
Undocumented |
Observed to exist but not in official docs. | Avoid in production; treat as unstable and unsupported. |
Removed |
No longer available. | No — kept only for history/migration. |
How we assign a status
Section titled “How we assign a status”- Start from Discord’s own signal (docs, changelog, “beta”/“preview” wording, allowlist notes).
- Downgrade confidence when we can’t verify against a primary source.
- Record the basis in the page’s
sourcesand, when non-obvious, in the decision log.
Related conventions
Section titled “Related conventions”- Last verified — the date the page’s claims were last checked. Facts drift; a stale date is a prompt to re-verify against the linked sources.
- Evidence callouts — inside pages, we distinguish Verified (checked against a source), Observation (first-hand behavior), and Hypothesis (plausible, unconfirmed). See CONTRIBUTING.
Undocumented never means “reverse-engineer private endpoints for production.”
See the Terms-of-Service boundary.