Discord error 50041: Invalid API version provided

The version segment in your request path (/api/v{n}/...) is not one Discord serves. Discord publishes a version table in the reference docs; very old versions (v3-v5) are discontinued, v6 and v7 are deprecated, and current development should target v10. Requesting a version that was removed, a future version that does not exist, or a malformed segment produces 50041.

You mostly see this from hand-built clients, very old library versions, or configuration that hard-codes the API base URL. Some libraries let you set apiVersion or rest.version; a typo there (for example v11) is enough. It can also come from a proxy or API gateway that rewrites paths.

{
  "message": "Invalid API version provided",
  "code": 50041
}

Do not hard-code API versions in application code; let the library own it and keep the library current. If you must pin, keep the version in one constant with a comment pointing at the versioning table in the Discord reference docs.

Add an integration test that hits GET /users/@me through your real HTTP layer on startup; a wrong version fails immediately and visibly instead of surfacing later in an unrelated feature. When upgrading API versions, read the changelog for removed fields and behavior changes, since a version bump is not purely a path change.

Version pinning is one of the few places where doing nothing is correct: let the library own the path. The REST and gateway version tables move together, so if you see this code after an infrastructure change, check the WebSocket side for 4012 too; both usually trace to the same stale base URL in one config file. Current version guidance sits with the REST limits on the Discord limits page.