Twitter oauth after connect GET Primary email address

[ojm37a]

Nice!

[chemitaxis]

HI! Do you know when the Identity Provider of Microsoft could obtain the email? Regards!

[slegay]

Could you please provide a link to the new documentation? Thx!

[andypiper]

we’ll announce here when ready.

[Basantk21]

Email addresses are not provided.

[ojm37a]

Any ETA on the announcement? I’ve got my OAuth connection to Twitter working and I’m waiting on the “GET Primary email address” functionality to continue with the project.

Thanks,
Owen

[bendavis78]

Hi, have the docs been added for this? It’s been a while now and still can’t seem to find them.

[mickey_ga]

Still waiting for news, I am writing an app to be ready on monday, will be a real problem if this feature is not going live!

[AnthonyIfon]

Any update or does anyone know a workaround

[Avaks]

Just wondering if there any news? Is email already somehow available through API?

[arkhipov]

So, it’s possible now to get email address via Twitter OAuth?

[andypiper]

Yes this is now available to whitelisted applications - details in the account/verify_credentials documentation.

[skylightit]

I have followed that link to verify our business account and I dont see the option to do so. We are a web app and need to have users email address for authentication.

[andypiper]

OK so the details are all there - you need to apply for whitelisting via the link on the documentation page. Once that has happened, add your privacy policy and ToS links, update your app permissions, and then call account/verify_credentials with the right set of parameters.

[skylightit]

Have gone through that page and I am not seeing any whitelisting options at all, see attached. Is that because we are in UK?

[andypiper]

Select “I need access to special authentication privileges” and in the form that appears, explain that you are requesting access to a user’s email address for your app. You’ll also be required to provide your app’s consumer key and the username of the account that it is registered to.

[pixabay]

It looks like support for web apps was either never there or has been removed. XAuth, which is required for retrieving an email address, is only available for desktop and mobile apps. The authorization form (https://support.twitter.com/forms/platform) explicitly states, no web apps are supported.

What’s up with that? Than kind of misses the whole point of this thread.

[andypiper]

“what’s up with that” - we simply haven’t been able to update the support form page yet.

XAuth is not required for accessing email and in fact is deprecated - we don’t recommend any apps use XAuth any more unless absolutely necessary as it does not support e.g. two-factor auth.

You absolutely can request that access to email address for a web app, just ignore that statement and explain the detail in your request.

[JibstaMan]

I’m having trouble retrieving the email address. I’ve gone through the process of requesting special authentication privileges (and I’ve received it). I have enabled “Request email addresses from users” within the Twitter app, as well as filled in links to the ToS and Privacy Policy. I’m not entirely sure what to do next. What do I need to do to retrieve the email address of the user?

Do I have to send a request to https://api.twitter.com/1.1/account/verify_credentials.json? I’ve tried this, but I keep getting back a “Bad authentication data.” error. I am including the Authentication header and “?include_entities=false&skip_status=1&include_email=true” query parameters.

I’m using NodeJS with passport-twitter. Passport-twitter requests user data using https://api.twitter.com/1.1/users/show.json (which succeeds), but this doesn’t return the email address. I’m using the same technique, but get a “Bad authenticated data.” error nonetheless.

Any help would be greatly appreciated.

[andypiper]

Do I have to send a request to https://api.twitter.com/1.1/account/verify_credentials.json? I’ve tried this, but I keep getting back a “Bad authentication data.” error. I am including the Authentication header and “?include_entities=false&skip_status=1&include_email=true” query parameters.

Yes, that is the correct endpoint to call (see the API docs). Note that you need to regenerate any existing tokens from before you were granted elevated privileges to request email address, as it states in the docs. If you’re getting a Bad Auth error then it sounds like there’s a problem with the OAuth setup on your call.

I’m not familiar with passport-twitter but will try to take a look when I have some time. A quick glance at the docs suggests that this just provides sign-in with Twitter functionality, and not a generalised Twitter API client - but I’m no expert in this library.