How to obtain user email through a Discord bot?

Other Questions Discord bot
1

I’ve set up a Discord bot that needs to get users’ email addresses for a specific task. I changed the OAuth scope to include email, but I’m still not seeing the email property in the user object.

Here’s what I’ve done:

  1. Updated my authorization URL to include the email scope
  2. Set up a test function to log the user object when a message is received
bot.on('messageCreate', (message) => {
  console.log(message.author);
});

When I run this, the user object doesn’t have an email field. It looks like this:

{
  id: '987654321098765432',
  username: 'CoolUser123',
  discriminator: '1234',
  avatar: 'abcdef1234567890',
  bot: false,
  // ... other properties, but no email
}

Am I missing something? How can I get the user’s email address through the bot? Any help would be great!

2

Getting user emails through a Discord bot isn’t straightforward. You can’t just access it from message events. Instead, you need to use OAuth2 with the ‘email’ scope. Set up an authorization flow where users grant permission. Once authorized, use the access token to fetch user data from the /users/@me endpoint. This should include the email if available. Keep in mind that not all users have verified emails, so you might get null values sometimes. Also, make sure your bot’s privacy policy clearly states how you’ll use email addresses to comply with data protection regulations.

3

hey there! to get user emails, u gotta use OAuth2 with the ‘email’ scope. make users go thru the auth process with that scope, then use the access token to hit the /users/@me endpoint. remember tho, not everyone has a verified email, so it might be null sometimes. good luck!

4

I recently tackled a similar issue and learned that you can’t simply extract emails from events such as message receives. Instead, you must integrate OAuth2 properly with the email scope. Begin by building an authorization URL that includes both the identify and email scopes and have users visit that URL. After authorization, exchange the provided code for an access token and then fetch the user’s data from the /users/@me endpoint. Note that not every user has a verified email, so you might encounter null values. It is also important to address data protection properly.