Note that there are some explanatory texts on larger screens.

plurals
  1. POTwitter API 1.1 OAuth Get Use Data
    text
    copied!<p>I read this tutorial to implement twitter oauth in nodejs (for "login with twitter" purpose) - <a href="http://codetheory.in/how-to-use-twitter-oauth-with-node-oauth-in-your-node-js-express-application/" rel="nofollow">http://codetheory.in/how-to-use-twitter-oauth-with-node-oauth-in-your-node-js-express-application/</a></p> <p>The last piece of code has this variable called <code>results</code> which is supposed to hold the user data sent back by twitter, but for me it only contains screen_name and user_id which is not enough. I need much more data like profile image, etc.</p> <p>So I looked at the twitter documentation - <a href="https://dev.twitter.com/docs/api/1/get/users/show" rel="nofollow">https://dev.twitter.com/docs/api/1/get/users/show</a><br> The sample URL seems to work fine - <a href="https://api.twitter.com/1/users/show.json?screen_name=TwitterAPI&amp;include_entities=true" rel="nofollow">https://api.twitter.com/1/users/show.json?screen_name=TwitterAPI&amp;include_entities=true</a></p> <p>But recently I read twitter will shut down API 1 soon and replace it with API 1.1</p> <p>So I tried the 1.1 API - <a href="https://dev.twitter.com/docs/api/1.1/get/users/show" rel="nofollow">https://dev.twitter.com/docs/api/1.1/get/users/show</a><br> The sample URL <strong>does not</strong> work - <a href="https://api.twitter.com/1.1/users/show.json?screen_name=rsarver" rel="nofollow">https://api.twitter.com/1.1/users/show.json?screen_name=rsarver</a> </p> <p>Gives error -</p> <pre><code>{"errors":[{"message":"Bad Authentication data","code":215}]} </code></pre> <p>What am I doing wrong ? How do I get user info properly from twitter and hopefully in my Node.js code that uses this module - <a href="https://github.com/ciaranj/node-oauth" rel="nofollow">https://github.com/ciaranj/node-oauth</a> ?</p> <p>Thanks in advance!</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload