A comprehensive Objective-C library for Twitter REST API 1.1
STTwitter will be presented at SoftShake 2013, Geneva, on October 24th.
- Installation
- Code Snippets
- Various Kinds of OAuth Connections
- OAuth Consumer Tokens
- Demo / Test Project
- Troubleshooting
- Developers
- Applications Using STTwitter
- BSD 3-Clause License
Drag and drop STTwitter directory into your project and that's it.
STTwitter compiles without modification with non-ARC projects. If the project uses ARC, add the -fno-objc-arc
flag to STTwitter files details here.
If you want to use CocoaPods, include the STTwitter pod in your project's podfile and install it:
pod 'STTwitter'
pod install
Note that STTwitter requires iOS 5+ or OS X 10.7+.
STTwitterAPI *twitter = [STTwitterAPI twitterAPIWithOAuthConsumerName:@""
consumerKey:@""
consumerSecret:@""
username:@""
password:@""];
[twitter verifyCredentialsWithSuccessBlock:^(NSString *username) {
// ...
} errorBlock:^(NSError *error) {
// ...
}];
[twitter getHomeTimelineSinceID:nil
count:100
successBlock:^(NSArray *statuses) {
// ...
} errorBlock:^(NSError *error) {
// ...
}];
[twitter getStatusesSampleDelimited:nil
stallWarnings:nil
progressBlock:^(id response) {
// ...
} stallWarningBlock:nil
errorBlock:^(NSError *error) {
// ...
}];
STTwitterAPI *twitter = [STTwitterAPI twitterAPIAppOnlyWithConsumerKey:@""
consumerSecret:@""];
[twitter verifyCredentialsWithSuccessBlock:^(NSString *bearerToken) {
[twitter getUserTimelineWithScreenName:@"barackobama"
successBlock:^(NSArray *statuses) {
// ...
} errorBlock:^(NSError *error) {
// ...
}];
} errorBlock:^(NSError *error) {
// ...
}];
You can instantiate STTwitterAPI
in three ways:
- use the Twitter account set in OS X Preferences or iOS Settings
- use a custom
consumer key
andconsumer secret
(three flavors)- get an URL, fetch a PIN, enter it in your app, get oauth access tokens
- set
username
andpassword
, get oauth access tokens with XAuth, if the app is entitled to - set
oauth token
andoauth token secret
directly
- use the Application Only authentication and get / use a "bearer token"
So there are five cases altogether, hence these five methods:
+ (STTwitterAPI *)twitterAPIOSWithFirstAccount;
+ (STTwitterAPI *)twitterAPIWithOAuthConsumerKey:(NSString *)consumerKey
consumerSecret:(NSString *)consumerSecret;
+ (STTwitterAPI *)twitterAPIWithOAuthConsumerKey:(NSString *)consumerKey
consumerSecret:(NSString *)consumerSecret
username:(NSString *)username
password:(NSString *)password;
+ (STTwitterAPI *)twitterAPIWithOAuthConsumerKey:(NSString *)consumerKey
consumerSecret:(NSString *)consumerSecret
oauthToken:(NSString *)oauthToken
oauthTokenSecret:(NSString *)oauthTokenSecret;
+ (STTwitterAPI *)twitterAPIAppOnlyWithConsumerKey:(NSString *)consumerKey
consumerSecret:(NSString *)consumerSecret;
Reference: https://dev.twitter.com/docs/ios/using-reverse-auth
The most common use case of reverse authentication is letting users register/login to a remote service with their OS X or iOS Twitter account.
iOS/OSX Twitter Server
--------------> reverse auth.
< - - - - - - - access tokens
-----------------------------> access tokens
<-------------- access Twitter on user's behalf
- - - - - - ->
Here is how to use reverse authentication with STTwitter:
STTwitterAPI *twitter = [STTwitterAPI twitterAPIWithOAuthConsumerName:nil
consumerKey:@""
consumerSecret:@""
username:@""
password:@""];
[twitter postReverseOAuthTokenRequest:^(NSString *authenticationHeader) {
STTwitterAPI *twitterAPIOS = [STTwitterAPI twitterAPIOSWithFirstAccount];
[twitterAPIOS postReverseAuthAccessTokenWithAuthenticationHeader:authenticationHeader
successBlock:^(NSString *oAuthToken, NSString *oAuthTokenSecret, NSString *userID, NSString *screenName) {
// ...
} errorBlock:^(NSError *error) {
// ...
}];
} errorBlock:^(NSError *error) {
// ...
}];
In Twitter REST API v1.1, each client application must authenticate itself with consumer key
and consumer secret
tokens. You can request consumer tokens for your app on Twitter website: https://dev.twitter.com/apps.
STTwitter demo project comes with TwitterClients.plist
where you can enter your own consumer tokens.
STTwitter demo (or test) project lets you choose how to get the OAuth tokens (see below).
Once you got the OAuth tokens, you can get your timeline and post a new status.
Twitter restricts the xAuth authentication process to xAuth-enabled consumer tokens only. So if you get an error like NSURLErrorDomain Code=-1012, Unhandled authentication challenge type - NSURLAuthenticationMethodOAuth2
while accessing https://api.twitter.com/oauth/access_token
then your consumer tokens are probably not xAuth-enabled. You can read more on this on Twitter website https://dev.twitter.com/docs/oauth/xauth and ask Twitter to enable the xAuth authentication process for your consumer tokens.
Please fill an issue on GitHub.
The application only interacts with STTwitterAPI
.
STTwitterAPI
maps Objective-C methods with all documented Twitter API endpoints.
You can create your own convenience methods with fewer parameters. You can also use this generic methods directly:
- (void)fetchResource:(NSString *)resource
HTTPMethod:(NSString *)HTTPMethod
baseURLString:(NSString *)baseURLString
parameters:(NSDictionary *)params
progressBlock:(void(^)(id json))progressBlock
successBlock:(void(^)(id json))successBlock
errorBlock:(void(^)(NSError *error))errorBlock;
+-------------------------------------------------+
| Your Application |
+-------------------------------------------------+
v
+-------------------------------------------------+
| STTwitterAPI |
+-------------------------------------------------+
v v v
+ - - - - - - - - - - - - - - - - - - - - - - - - +
| STTwitterOAuthProtocol |
+ - - - - - - - - - - - - - - - - - - - - - - - - +
v v v
+-------------+----------------+------------------+
| STTwitterOS | STTwitterOAuth | STTwitterAppOnly |
| +----------------+------------------+
| | STHTTPRequest |
+-------------+-----------------------------------+
|
+ Accounts.framework
+ Social.framework
* STTwitterAPI
- can be instantiated with the authentication mode you want
- provides methods to interact with each Twitter API endpoint
* STTwitterOAuthProtocol
- provides generic methods to POST and GET resources on Twitter hosts
* STTwitterOS
- uses Twitter accounts defined in OS X Preferences or iOS Settings
- uses OS X / iOS frameworks to interact with Twitter API
* STTwitterOAuth
- implements OAuth and xAuth authentication
* STTwitterAppOnly
- implements the 'app only' authentication
- https://dev.twitter.com/docs/auth/application-only-auth
* STHTTPRequest
- block-based wrapper around NSURLConnection
- https://github.com/nst/STHTTPRequest
- Adium developers have chosen to use STTwitter to handle Twitter connectivity in Adium, starting from version 1.5.7.
Copyright (c) 2012-2013, Nicolas Seriot All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
- Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
- Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
- Neither the name of the Nicolas Seriot nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.