discordjs/discord-api-types

docs: several broken links across library need updating

Open

#1,533 opened on Feb 20, 2026

View on GitHubContributor guide
 (10 comments) (0 reactions) (0 assignees)TypeScript (140 forks)auto 404
buggood first issue

Repository metrics

Stars
 (619 stars)
PR merge metrics
 (PR metrics pending)

Description

Issue description

I believe the recent update to Discord's documentation site may have lead to various links in this package being broken as a result.

Below are some examples of only the links that I found were broken. I suspect there could be more and am not entirely aware of the full scope that this has affected the docs here yet - some links seem to work just fine, and some are broken.

E.x.:

https://github.com/discordjs/discord-api-types/blob/6b6b256d5fc70d2cedb3613b5f52b3de06510ede/gateway/v10.ts#L1-L3

https://github.com/discordjs/discord-api-types/blob/6b6b256d5fc70d2cedb3613b5f52b3de06510ede/gateway/v10.ts#L121-L125

...and in other versions: https://github.com/discordjs/discord-api-types/blob/6b6b256d5fc70d2cedb3613b5f52b3de06510ede/gateway/v6.ts#L2

...and in payloads: https://github.com/discordjs/discord-api-types/blob/6b6b256d5fc70d2cedb3613b5f52b3de06510ede/payloads/v10/application.ts#L221-L223

I'm not sure as to whether there is an automated process to this - I can imagine it being quite challenging to go through everything.

I did want to raise this as it does affect the library quite severely; many links will 404 which can significantly hurt developer experience.

Code sample

N/A

Package version

0.38.40

Runtime

Node.js

Runtime version

v25.2.1

Priority this issue should have

Medium (should be fixed soon)

Contributor guide

Research direction
Identify all broken links in the documentation files by checking the URLs that return 404 and update them to the correct Discord documentation URLs.
Tech stack
typescript
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90