Hi all,
Nowadays, important sites on web are growing their presence in mobile space. As usual, a quick way to go in this direction is releasing mobile versions of their sites. On the other hand, they also use to provide means so third-party sites and apps can access their content and services. For instance, many sites (or platforms), e.g., Google, Yahoo,
Facebook
,
Twitter
, etc, provide APIs, so that developer can build their products that rely on content from them.
To start accessing any content or service from one of those sites, you first need to authenticate with it. The site needs to recognize you so it can open their doors for you. The type of authentication may vary depending on each site. It is commom to encounter with
Http Basic Auth, which is very easy to work with. However, most services are shifting to
OAuth. A more secure auth mechanism that also avoids third-party sites have access to user's credentials. Recently, Twitter turned off its Http Basic Auth, to support only OAuth. Some sites still work with both, but it is matter of time so they keep only OAuth.
Due to some aspects of OAuth, its pure implementation is not feasible for desktop and mobile apps. This is related to a spec flow that demands your app to be redirected forth/back to/from a login page. It is kind of complicated to accomplish that in a mobile app, for instance. To avoid this step, they created
xAuth, which is same as OAuth, but the login page flow.
An OAuth request is quite more complicated to perform, since it requires a signature for the request, which uses some hash algoritms and encoders. To now more about it, click
here.
In my
Twitter API ME project, I had to implement it, since as I previously said, Twitter turned off Http Basic Auth. However, my xAuth implementation was designed to be reused by other apps and frameworks. So, if you are looking for xAuth lib for your app, you are at the right place. So, to start it up, download the latest version of Twitter API ME at
www.twitterapime.com.
Below I will put some code snippets that demonstrate how to get authenticated to Twitter and then post a tweet. After downloading the API, you will need to obtain your app's OAuth keys: consumer key and secret. They will be used to produce that signature I mentioned ealier. Those keys are provided by the site you want to connect with, after a quick subscription. Let's show some code:
01. HttpRequest req = new HttpRequest("https://api.twitter.com/oauth/access_token");
02. req.setMethod(HttpConnection.POST);
03. XAuthSigner signer = new XAuthSigner("", "");
04. signer.signForAccessToken(req, "", "");
05. try {
06. HttpResponse resp = req.send();
07. if (resp.getCode() == HttpConnection.HTTP_OK) {
08. Token accessToken = Token.parse(resp.getBodyContent());
09. req.close();
10. req = new HttpRequest("http://api.twitter.com/1/statuses/update.xml");
11. req.setMethod(HttpConnection.POST);
12. req.setBodyParameter("status", "");
13. req.setSigner(signer, accessToken);
14. resp = req.send();
15. }
16. } catch (IOException e) {
17. e.printStackTrace();
18. } finally {
19. try {
20. req.close();
21. } catch (IOException e) {}
22. }
Basically what we do is to sign each request, using
XAuthSigner class, as we see in the lines 4 and 13. As soon as you get authenticated, you will obtain your access token (line 8). From this point on, every request will be signed using your keys and token. This token, in turn, can be stored for further use. It avoids requesting user's credentials next time and skip auth step.
I recommend before trying to access any site using xAuth, that read its documentation first, so you can see whether they require an additional procedure to work with xAuth. I am mentioned that, because Twitter, for instance, demands us to send an e-mail to them requesting privileges to use xAuth in our apps. Otherwise, it will not work. So be aware of that.
So, that's all guys! I hope it be useful for all of you.
See you in the next post...
support implementation. As you may know, Twitter API
is shutting down the Http Basic Auth support on June 30th, 2010. This way, we had to run to get it done, otherwise, the API would work from this date. But we made it and now it is time to download to keep the things running.
and Sun Microsystems. But do not worry! Even after April 30th, you can download the new version. :)
were also implemented for all new features to guarantee the quality. Now we have over 100 test cases, covering 91% of the code.
Basic Authentication method to authenticate to Twitter API
1.1 support for all the features
have been implemented to ensure that no bug comes up after any change. Currently, we have 91 test cases covering 69% of the code. The objective for the next version is to increase this percentage as much as possible.
API ME 1.0? Yes? Great!!! To help still more, I just developed a sample app, Sparrow, so you guys can have a better understanding on how this API works. For while, it only provides a functionality for searching tweets. For instance, you enter some filters and then the application shows the results.
API ME's announcement post, here it goes some code snippets to demonstrate how to use this API. In fact, I will consider this post as a first tutorial on Twitter API ME that will help you to get started. First of all, I will show you how to create a simple query, submit it to Twitter Search API and then present the result. So you will not see much detail in this quick tutorial. Actually, I am thinking of dedicating more posts to explain each class in detail. But for now, let's just see how it works.
APIs. Twitter API ME 1.0 just supports Search API services. So, for now, you will work with the package com.twitterapime.search only. This package contains all the classes that are responsible for submitting a query to Twitter and then getting the result. These are the main classes:
