Discussion around the release of application-only authentication

HarshithSK · 2013-07-18T12:59:03.000Z

sickweather · 2013-09-03T19:14:56.000Z

Hi everyone,
Ever since this change occurred on 3/11/13 my company Sickweather has seen a huge decrease in the number of internationally geocoded tweets that we collect using the REST API. For example, from 1/1/13 - 3/10/13 we saw a regular volume of tweets in the UK for a specific health-related keyword at around 140 tweets/day. On 3/11/13 that dropped down to an average of 3 tweets/day. It only seems to be affecting non-US tweets. How might this issue be connected to this application-only authentication changes?

Cathal_Farrell · 2013-10-24T10:22:25.000Z

Hi all, I need to build an iOS app that pulls in a read-only stream of tweets from my client’s account. I am pretty new to it all, and getting overwhelmed with all the discussions on API 1.1 in general. I had working code but it requires access to the user’s twitter account through iPhone settings. Now I have been told that I need to cater for users of the app that don’t have Twitter accounts and just want to browse the tweets from my client. I suspect that Application Only Authentication is what is required, but haven’t found how to set it up from an iOS app yet. Any guidance would be wonderful, while I keep on searching. Thanks in advance.

episod · 2013-10-24T15:04:28.000Z

App-only auth would be the right use case for this, but it’s not well-suited to distributed client scenarios – the rate limits are low enough that with many simultaneous users, you’re rate limits would likely be depleted rather quickly. It is better to use app-only auth server side and have your application obtain the relevant tweets securely from your servers, provided you have them.

vitaliykulikov · 2013-12-07T02:45:00.000Z

still have issue
POST https://api.twitter.com/oauth2/token 403 (Forbidden)

TwittV2 · 2013-12-13T15:39:02.000Z

Hi,
I want to implement below scenario, and get 401 error, please provide your suggestion for the same.

1.] Twitter api - user authenticated using mobile app.
2.] php server will store the token and secret.
3.] when php server want to post on behalf of mobile user, it gives 401 error.

Can you please suggest what i am doing wrong here.
Thanks

ghorpade_sandip · 2014-01-28T11:52:00.000Z

I am new to twitter application development and not able formulate header for GET requests. I am using application only authentication method and working on Windows application in C#
. What will be the HTTP header format for “https://api.twitter.com/1.1/statuses/mentions_timeline.json” using Bearer token?

ghentsch · 2016-01-25T22:33:49.341Z

Is application-only authentication rate limits based on ip? That is, does each ip making the call get the standard rate limit for the application?

Our scenario is we have an application which does twitter searches. We have a parser which does the searches and pulls them into our database to be used by our customers. Each customer would run their own parser and I’d hope that each would have their own rate limit.

Currently, we’re using user auth to deal with this but application-only auth is really what makes sense.

joncipriano · 2016-01-29T21:13:38.438Z

Using application-only auth, the rate limit is a applied to the app. If you provide a user context, the limit is applied to the user the access tokens were generated for.

If you want your customers to have there own rate limits you should provide a user context.

Will close this thread as it’s pretty old now and covers too many subjects. If you have more questions open a thread for your specific issue. Thanks!

joncipriano · 2016-01-29T21:13:45.212Z