2

I've been trying to connect AngularJS and Twitter API. It all started with following the instructions on John Lindquist's video on AngularJS twitter search. Which is basically the following code

var app = angular.module("MyApp", ["ngResource"]);

function MyCtrl($scope, $resource) {
  var TwitterAPI = $resource("http://search.twitter.com/search.json",
    { callback: "JSON_CALLBACK" },
    { get: { method: "JSONP" }});

  $scope.search = function() {
    $scope.searchResult = TwitterAPI.get({ q: $scope.searchTerm });
  };
}

But the problem is, this generates a 401 Unauthorized. A few searches on google revealed that Twitter had changed its API since this tutorial had been posted. I found another article on using OAuth2 with AngularJS to access Twitter. Which has the following

var consumerKey = encodeURIComponent('<your consumer key>')
var consumerSecret = encodeURIComponent('<your consumer secret>');
var credentials = Base64.encode(consumerKey + ':' + consumerSecret);

// Twitters OAuth service endpoint
var twitterOauthEndpoint = $http.post(
  'https://api.twitter.com/oauth2/token'
  , "grant_type=client_credentials"
  , {headers: {'Authorization': 'Basic ' + credentials, 'Content-Type': 'application/x-www-form-urlencoded;charset=UTF-8'}}
);

However this also ended up with the following error on the console

> OPTIONS https://api.twitter.com/oauth2/token 405 (Method Not Allowed) 
> XMLHttpRequest cannot load https://api.twitter.com/oauth2/token. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://127.0.0.1:3000' is therefore not allowed access.

I've gone this far, but don't know what to do next to get search results using $resource from twitter. Don't know if this helps, but I'm also using Firebase.

NSCoder
  • 1,594
  • 5
  • 25
  • 47

4 Answers4

1

You might be getting this error because you are trying to do a POST request, instead of a GET request:

    var twitterOauthEndpoint = $http.get(
  'https://api.twitter.com/oauth2/token'
  , "grant_type=client_credentials"
  , {headers: {'Authorization': 'Basic ' + credentials, 'Content-Type': 'application/x-www-form-urlencoded;charset=UTF-8'}}
);

In general, whenever you get 405, it's because you are using the wrong method, just like the error mentions.

Checkout ng-twitter by darul75, it looks like it does what you need, and if not, it can be a good source to read :) Here's the demo page.

Edit: I ignored the second console error. If you are running your app directly from a file, try switching to a local server (or even dropbox's public folder).

GabrielG
  • 454
  • 4
  • 12
  • The demo runs http request against its own domain though ( `http://darul-demo.herokuapp.com/search?hashtag=football` ) not the twitter API – Philipp Gayret Jun 14 '14 at 17:56
  • 1
    Or as the readme states `"So one thing you need to do on your own is the server side."`, as the author of the thing also faced CORS issues which is what this question is about – Philipp Gayret Jun 14 '14 at 17:58
  • @GabrielG ng-twitter is great but I still need the core twitter api as my main concern is searching through [twitter users](https://dev.twitter.com/docs/api/1.1/get/users/lookup) not tweets once I can get OAuth to get me authenticated. – NSCoder Jun 14 '14 at 18:02
  • Right, my bad.. anyway, you absolutely do not have to run your app under the Twitter domain to use their REST API :) – GabrielG Jun 14 '14 at 18:02
  • @NSCoder, where are you running your app from? is it form a local server or directly through a file? – GabrielG Jun 14 '14 at 18:04
  • I'm running a [yeoman](http://yeoman.io) App using [gruntJS](http://gruntjs.com). – NSCoder Jun 14 '14 at 18:10
  • Here's something worth trying - try adding "http://127.0.0.1" as your app's domain. You will later be able to change it. I have a strong feeling about this – GabrielG Jun 14 '14 at 19:05
1
XMLHttpRequest cannot load https://api.twitter.com/oauth2/token.
No 'Access-Control-Allow-Origin' header is present on the requested resource.
Origin 'http://127.0.0.1:3000' is therefore not allowed access.

This means that from http://127.0.0.1:3000 your browser will not allow JavaScript to get results from the HTTP call. Futher No 'Access-Control-Allow-Origin' header is present indicates that this goes for every domain you could call from ( Except api.twitter.com ).

Reading through the OAuth API documentation I haven't been able to find anything else than people asking how to perform CORS requests and that they're unable to call the API from the browser. All JavaScript Twitter libraries are NodeJS, which is server side.

GabrielG also makes a point that the call is returning an https://api.twitter.com/oauth2/token 405 (Method Not Allowed) which means that the browser cannot do a lookup of wheter it's allowed to do a POST, it does this with the OPTIONS method. This does not mean that you shouldn't be using POST

Philipp Gayret
  • 4,870
  • 1
  • 28
  • 34
0

The twitter no more supports the way blog explained to query. Twitter changed it's API and now you need to authenticate/authorize for every such request. There is working example present here

https://blog.twitter.com/2014/rendering-tweets-with-angularjs-and-nodejs

This will require your app and secret keys and access and secret keys. this will allow you to fetch results. I hope this will help. There is good information about this is available here also

https://beautifulbytes.wordpress.com/2013/06/18/oauth2-with-angularjs-to-access-twitter/

Mohammad Adnan
  • 6,527
  • 6
  • 29
  • 47
0

This blogpost works. http://www.sitepoint.com/building-twitter-app-using-angularjs/

Basically, you can't just query the twitter search API. You need to go to https://apps.twitter.com/ to set up an app to be able to communicate with the API, and then you need to use oauth as well (I personally created an account with oauth.io).

It's all in the blogpost.

After the basic stuff I would recommend reading the twitter api docs: https://dev.twitter.com/rest/public

I know your post is old, but there was no accepted answer, so hopefully this helps :)

Cody Jacques
  • 506
  • 5
  • 9