> For the complete documentation index, see [llms.txt](https://agpt.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agpt.co/docs/integrations/block-integrations/oauth_blocks.md).

# Discord OAuth Blocks

Blocks for Discord OAuth2 authentication and retrieving user information.

## Discord Get Current User

### What it is

Gets information about the currently authenticated Discord user using OAuth2 credentials.

### How it works

This block uses Discord's OAuth2 API to retrieve information about the currently authenticated user. It requires valid OAuth2 credentials that have been obtained through Discord's authorization flow with the `identify` scope.

The block queries the Discord `/users/@me` endpoint and returns the user's profile information including their unique ID, username, avatar, and customization settings like banner and accent color.

### Outputs

| Output        | Description                             | Type |
| ------------- | --------------------------------------- | ---- |
| error         | Error message if the operation failed   | str  |
| user\_id      | The authenticated user's Discord ID     | str  |
| username      | The user's username                     | str  |
| avatar\_url   | URL to the user's avatar image          | str  |
| banner\_url   | URL to the user's banner image (if set) | str  |
| accent\_color | The user's accent color as an integer   | int  |

### Possible use case

**User Authentication**: Verify user identity after OAuth login to personalize experiences or grant access.

**Profile Integration**: Display Discord user information in external applications or dashboards.

**Account Linking**: Connect Discord accounts with other services using the unique user ID.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://agpt.co/docs/integrations/block-integrations/oauth_blocks.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.