What Is Userdoccers and What Does the Unofficial Discord User API Documentation Cover?

Userdoccers is the community-maintained, unofficial documentation for the user side of the Discord API, hosted at docs.discord.food. It covers how the API behaves for non-bot users — specifically requests made with user and bearer authentication tokens, as used by the official client and developer portal. It is not affiliated with or endorsed by Discord, and its contents are largely based on reverse engineering and educated guesses, so inaccuracies are possible. If you need bot endpoints, interactions, or any guarantee that an endpoint won't break, this is the wrong resource; use Discord's official documentation instead.

What Userdoccers actually documents

The scope is deliberately narrow. According to the introduction, the project documents "the user side of the Discord API, which is not officially supported, as used by the official client and developer portal."

That means:

• User and bearer authentication tokens are the focus, not bot tokens.
• Client-facing behavior — the same routes the official client relies on — is what gets described.
• Bot endpoints may appear, but how bots interact with the API is explicitly not the point of the documentation.

If your goal is a bot, an interaction handler, or anything with a stability promise, the introduction points you to Discord's official documentation rather than this project.

Why the information comes with caveats

The introduction is unusually direct about its own reliability. Two limitations matter before you build anything on top of it:

1. Reverse engineering and guesswork. The maintainers state they try not to publish anything without basis, but "quite a lot of the documentation contents are based off of reverse engineering and educated guesses," so inaccuracies may be present.
2. No official backing. The project is not affiliated with or endorsed by Discord in any way.

Treat the pages as a map of observed behavior, not a contract. Endpoints can change without notice, and a documented field may not match what you see in practice.

The Terms of Service risk

The introduction includes a plain warning: automating user accounts is against the platform Terms of Service, and doing so unsafely might get you banned.

This is the single most important constraint for anyone considering the documentation. Reading it is harmless; building a self-bot or automating your own account is a different matter. The documentation describes how the user API works — it does not make that use permissible.

Where to send corrections and bug reports

The project is community-driven and hosted on GitHub, and the introduction explicitly invites contributions:

• Corrections and improvements to the documentation are welcome; see CONTRIBUTING.md in the repository.
• Bugs in bot-accessible parts of the API should go to the official documentation's issue tracker, not this project.

If you have knowledge of the Discord API, contributing is framed as the thing that keeps the project useful.

When to use it — and when not to

The practical takeaway: Userdoccers is a reference for understanding the user-facing API, useful for research and for filling gaps the official docs don't cover. It is not a foundation for production systems, and it is not a green light to automate a user account.