Re: [twitter-dev] Consumer Key and Secret is not Working
Post some code. --Regards, Denzil On Mon, Jul 4, 2011 at 1:05 PM, vicky bajaj vicky.baja...@gmail.com wrote: I have already have an application which is working for particular set of Consumer Key and Secret, but due to unavailability of A/C information I can't get the further details. So I have created one new app and with another account and used the Consumer Key and Secret of newly created app, but I am continuously getting 401 Unauthorized access. Please suggest what should I do?? Thanks Regards Vicky -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Rate limit exceeded. Clients may not make more than 150 requests per hour
Please read the Rate Limiting documentation carefully. You need to make OAuth requests to increase your rate to 350 per hour. Whitelisting is no longer permitted. --Regards, Denzil On Mon, Jul 4, 2011 at 6:05 PM, Tushar gandhi.t...@gmail.com wrote: I am new to twitter API. I am retrieving the tweets of a particular user. It was working yesterday but some how from morning I am getting this errror:- Rate limit exceeded. Clients may not make more than 150 requests per hour -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Poor documentation. For example, regarding lists. Suggestions for improvement.
Matt :
I suggest in the Example Requests you add the URL for the call. It will
prevent much of the What URL to call? queries.
--Regards,
Denzil
On Fri, Jun 24, 2011 at 4:55 AM, Matt Harris thematthar...@twitter.comwrote:
Hi Dave,
Thanks for your feedback, it's important for us to know when developers are
not finding the information they are looking for.
I have responded to your specific points inline:
Issue #1: Valid version numbers
I was unable to locate valid values for version. I tried 1.1.14,
which I understand the current version to be from searching the site,
but that causes a 404. It was only after digging around for examples
that I noticed people using 1. A page describing valid version
numbers should be linked from the word version.
In the API documentation there is a version place marker in the example
request URL. Currently only one version of the API exists, that version is
1. This means any REST API queries will be of the format:
https://api.twitter.com/1/statuses/user_timeline.json
I've updated the API FAQ and Things Every Developer Should Know pages
to include this information.
http://dev.twitter.com/pages/every_developer
https://dev.twitter.com/pages/api_faq
Issue #2: Extremely unclear parameter passing
As this call uses GET, and the documentation lists parameters you
should include, this implies to me that you should use a query string.
The docs list the following required parameters:
* list_id - The numerical id of the list.
* slug - You can identify a list by its slug instead of its numerical
id. If you decide to do so, note that you'll also have to specify the
list owner using the owner_id or owner_screen_name parameters.
As it is not at all obvious how you discover the list_id or
owner_id, I opted to use slug and owner_screen_name. However, if
you
$ curl
http://api.twitter.com/1/lists/statuses.json?owner_screen_name=cnnslug=cnnnews
you get
{error:You must specify either a list ID or a slug and
owner,request:\/1\/lists\/statuses.json?owner_screen_name=cnn}
Notice that the response json lists the request with only the
owner_screen_name parameter. I imagine that 1 or more things went
wrong, possibly including:
1. The API has a bug that is stripping the second parameter
2. The documentation is incorrect, and you may not use slug and
owner_screen_name to retrieve results.
3. The documentation does not properly describe how you pass the
arguments in the query string. Perhaps you're supposed to encode the
entire string. I was not able to discern this.
4. The documentation is incorrect about the url format.
The request you are making is correct. The error is instead being caused by
the way in which you are using your terminal. When using a terminal like
this you need to remember to either quote your URL or escape the 's.
This would make your request look like this:
curl
http://api.twitter.com/1/lists/statuses.json?owner_screen_name=cnnslug=cnnnews
Issue #3: No obvious way to discover list_id or owner_id
user_ids are provided in all API responses which include a user object. The
most common way of getting information about a user is through the
users/show method or users/lookup method:
http://dev.twitter.com/doc/get/users/show
http://dev.twitter.com/doc/get/users/lookup
list_id is available from the index of lists for a user. This request is
the /1/lists request:
http://dev.twitter.com/doc/get/lists
Alternatively, if those values are unknown or you don't wish to look them
up, you can provide the slug and screen_name as you have done in your
example.
Issue #4: Undocumented, un-obvious correct url
I was finally able to retrieve the results using this url, pieced
together from scattered examples.
$ curl http://api.twitter.com/1/cnn/lists/cnnnews/statuses.json
So far as I could tell, the documentation in no way implies that you
could use such a url.
This is the deprecated way of making lists requests. It is documented on
this page of the developer resources site:
http://dev.twitter.com/doc/get/:user/lists/:id/statuses
I hope that helps explain a little bit more about the API. Let me know if
this information is useful or what you would change and we'll see how we can
incorporate it into the docs.
Best,
@themattharrishttps://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your
[twitter-dev] User suggestions and User Suggestions Twitter
Hi, I am unable to understand the API for user/suggestionshttp://dev.twitter.com/doc/get/users/suggestionsand user/suggestions/twitterhttp://dev.twitter.com/doc/get/users/suggestions/:slug resources. It would be great if you highlight two particular aspects : 1. What do these API calls signify? 2. Example calls for both of these API resources Thanks, --Regards, Denzil -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] rate limiting on users profile image
DT :
http://dev.twitter.com/pages/rate-limiting#rest
API methods which are not directly rate limited are still subject to
organic, unpublished limits. This includes actions like publishing status
updates, direct messages, follow/unfollow actions, etc. These Twitter
Limitshttp://support.twitter.com/forums/10711/entries/15364 are
described on our help site
I think this says it all.
--Regards,
Denzil
On Wed, Jun 8, 2011 at 11:26 PM, dt dtip...@gmail.com wrote:
According to the current docs, the users/profile_image path is not
currently rate limited:
http://dev.twitter.com/doc/get/users/profile_image/:screen_name
But when I access this method, I'm sometimes getting rate limit
errors:
{error:Rate limit exceeded. Clients may not make more than 150
requests per hour.,request:\/1\/users\/profile_image\/tw.json?
size=bigger}
Has this policy been updated, and the docs are behind? (I work in a
place where a single IP is shared for the whole building, so rate
limits are exceeded a lot of the time when I'm testing)
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] rate limiting on users profile image
Matt :
Can you also clear the air on what the snippet from the Twitter docs mean? I
read it as there are no non-rate limited methods.
http://dev.twitter.com/pages/rate-limiting#rest
API methods which are not directly rate limited are still subject to
organic, unpublished limits. This includes actions like publishing status
updates, direct messages, follow/unfollow actions, etc. These Twitter
Limitshttp://support.twitter.com/forums/10711/entries/15364 are
described on our help site
--Regards,
Denzil
On Thu, Jun 9, 2011 at 12:45 AM, Matt Harris thematthar...@twitter.comwrote:
Hey,
This endpoint has always been rate limited so this is an error in the docs.
We have some updates to the docs coming out soon which will correct that.
Best,
@themattharrishttps://twitter.com/intent/follow?screen_name=themattharris
Developer Advocate, Twitter
On Wed, Jun 8, 2011 at 10:56 AM, dt dtip...@gmail.com wrote:
According to the current docs, the users/profile_image path is not
currently rate limited:
http://dev.twitter.com/doc/get/users/profile_image/:screen_name
But when I access this method, I'm sometimes getting rate limit
errors:
{error:Rate limit exceeded. Clients may not make more than 150
requests per hour.,request:\/1\/users\/profile_image\/tw.json?
size=bigger}
Has this policy been updated, and the docs are behind? (I work in a
place where a single IP is shared for the whole building, so rate
limits are exceeded a lot of the time when I'm testing)
--
Twitter developer documentation and resources:
https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker:
https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] get the profile of those who clicked the link on twitter
A hack around would be to distribute your profile link URL as goo.gl or bit.ly and get statistics from their respective APIs. --Regards, Denzil On Thu, Jun 9, 2011 at 1:24 AM, Nalin Savara nsn...@gmail.com wrote: On Thu, Jun 9, 2011 at 1:14 AM, Cleimar Vidal cleimarvi...@hotmail.com wrote: have any way of knowing who clicked??... Em 08/06/2011, às 16:37, Scott Wilcox escreveu: Heya Neandertal, Cleimar, ... No, there is no way to know... Who clicked profile link on twitter. Regards, Cro-Magnon Nalin -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] get the profile of those who clicked the link on twitter
Cleimar : No, not possible. --Regards, Denzil On Thu, Jun 9, 2011 at 6:32 AM, Cleimar Vidal cleimarvi...@hotmail.comwrote: would make such a script in php to get the User or the id of the twitter profile to see as many times he visited my profile url? -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Twitter search API rate limit hit
--Regards, Denzil On Wed, Jun 8, 2011 at 1:47 AM, Orion Richardson ori...@gmail.com wrote: Hi all, I just built a new application which leverages the Twitter search API. Looks like I've been rate limited almost immediately... In my case, I'm trying to search for URLs being tweeted and retweeted on behalf of users on our site. It seems like the only option is the search API, since none of the other APIs follow URL shortners. Am I correct in that? I think the Streaming API does provide results for URL shorteners if that's what you meant. Is there any way to get the rate limit increased for a given application or some alternative I'm missing? https://dev.twitter.com/doc/get/account/rate_limit_status What was the result on the rate limit status call? Thanks in advance, Orion Foragr - http://foragr.com/ -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Oauth Rate Limit 150 per hour?
Hi,
I am performing OAuth to sign my requests. I am not developing a web
app. I am trying to harvest some user data. Here's what I do :
import oauth2 as oauth
import time
CONSUMER_KEY = 'xx'
CONSUMER_SECRET = 'xx'
access_key = 'xx'
access_secret_key = 'xxx'
consumer = oauth.Consumer(CONSUMER_KEY, CONSUMER_SECRET)
token = oauth.Token(access_key, access_secret_key)
client = oauth.Client(consumer)
# Set the API end point
url = 'http://api.twitter.com/1'
params = {'oauth_version': 1.0,
'oauth_nonce': oauth.generate_nonce(),
'oauth_timestamp': int(time.time()),
'oauth_token': access_key,
'oauth_consumer_key': consumer.key,
'screen_name' : 'denzil_correa'
}
req = oauth.Request(method=GET, url=url, parameters=params)
# Sign the request.
signature_method = oauth.SignatureMethod_HMAC_SHA1()
req.sign_request(signature_method, consumer, token)
### Make the auth request ###
test = 'http://api.twitter.com/1/account/rate_limit_status.json'
resp, content = client.request(test, GET)
print resp
print content # prints 'ok'
Here's the output:
{reset_time:Mon Jun 06 14:54:50 +
2011,remaining_hits:132,hourly_limit:150,reset_time_in_seconds:1307372090}
Am I missing something?
--Regards,
Denzil
--
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth Rate Limit 150 per hour?
Is that Python? : Yes 1. You aren't signing using the proper url. Is the end point URL wrong? 2. You aren't using anything related to the signature on the request (req) I am a newbie to Python. I am trying to dabble using OAuth. I understand the OAuth flow but somehow what I am doing seems a bit tangential to what OAuth is meant for. What should I do to rectify it ? --Regards, Denzil On Mon, Jun 6, 2011 at 8:16 PM, Tom van der Woerdt i...@tvdw.eu wrote: You aren't using anything related to the signature on the request (req). -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth Rate Limit 150 per hour?
Tom : Thanks for the reply. 1. You don't sign the test variable, you sign the URL variable, which isn't an endpoint. I have changed the same 2. You don't use the req variable to make the request, but instead you create a new connection which is completely unrelated to the signed request. I don't understand this point. What's the change am I supposed to make ? I have opened up a gist for easier editing : https://gist.github.com/1010430 --Regards, Denzil On Mon, Jun 6, 2011 at 8:30 PM, Tom van der Woerdt i...@tvdw.eu wrote: 1. You don't sign the test variable, you sign the URL variable, which isn't an endpoint. 2. You don't use the req variable to make the request, but instead you create a new connection which is completely unrelated to the signed request. -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth Rate Limit 150 per hour?
Tom : Are you sure? This gives me a : Traceback (most recent call last): File oauth_test.py, line 41, in module resp, content = req.request(url, GET) AttributeError: 'Request' object has no attribute 'request' --Regards, Denzil On Mon, Jun 6, 2011 at 8:49 PM, Tom van der Woerdt i...@tvdw.eu wrote: On 6/6/11 5:10 PM, Correa Denzil wro -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth Rate Limit 150 per hour?
Well, it turns out it's not the case. Both the points you mentioned weren't the issue as I see it. The issue was while I was creating the client I wasn't supplying the token. Check Line 20 in the gist. https://gist.github.com/1010430 --Regards, Denzil On Mon, Jun 6, 2011 at 8:58 PM, Correa Denzil mcen...@gmail.com wrote: Tom : Are you sure? This gives me a : Traceback (most recent call last): File oauth_test.py, line 41, in module resp, content = req.request(url, GET) AttributeError: 'Request' object has no attribute 'request' --Regards, Denzil On Mon, Jun 6, 2011 at 8:49 PM, Tom van der Woerdt i...@tvdw.eu wrote: On 6/6/11 5:10 PM, Correa Denzil wro -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth Rate Limit 150 per hour?
Yes, it works. Thanks :-) --Regards, Denzil On Mon, Jun 6, 2011 at 9:10 PM, Tom van der Woerdt i...@tvdw.eu wrote: In that case, try removing everything related to the req variable. Seems it's all unrelated to the actual request (unless the oauth library is very badly designed, of course). Line 22 all the way up to 35. Tom On 6/6/11 5:38 PM, Correa Denzil wrote: Well, it turns out it's not the case. Both the points you mentioned weren't the issue as I see it. The issue was while I was creating the client I wasn't supplying the token. Check Line 20 in the gist. https://gist.github.com/1010430 --Regards, Denzil On Mon, Jun 6, 2011 at 8:58 PM, Correa Denzilmcen...@gmail.com wrote: Tom : Are you sure? This gives me a : Traceback (most recent call last): File oauth_test.py, line 41, inmodule resp, content = req.request(url, GET) AttributeError: 'Request' object has no attribute 'request' --Regards, Denzil On Mon, Jun 6, 2011 at 8:49 PM, Tom van der Woerdti...@tvdw.eu wrote: On 6/6/11 5:10 PM, Correa Denzil wro -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth in Twitter via Python
Tom : Thanks. I will create multiple user accounts. I guess about 20 (350 * 20 = 7000 considering 1 request per second) should solve my issue. --Regards, Denzil On Sat, Jun 4, 2011 at 3:35 AM, Tom van der Woerdt i...@tvdw.eu wrote: If you authenticate, all requests (except for search) will go into the 350 requests. If you want 500, then perform 150 unauthenticated and 350 authenticated. If you need even more, use more accounts to do the requests. Tom On 6/3/11 11:06 PM, Correa Denzil wrote: Ah! I feel similar. Which essentially means that despite acquiring data which is publicly available I will be limited to 150 requests per hour and even OAuth will not help increasing it to 350 ? --Regards, Denzil On Sat, Jun 4, 2011 at 2:32 AM, James Giffordja...@jamesrgifford.com wrote: The way I'm reading it it falls under 1. But I might be mistaken. --James Gifford http://jamesrgifford.com On Jun 3, 2011, at 17:01, Correa Denzilmcen...@gmail.com wrote: Hi, I am collecting Twitter data for my research. The API says that : [1] Anonymous calls are based on the IP of the host and are permitted 150 requests per hour. This classification includes unauthenticated requests (such as RSS feeds), and authenticated requests to resources that do not require authentication. [2] OAuth calls are permitted 350 requests per hour. I want to seek a clarification on point [1]. Lets say I want to access a list of followers of a user id (which is public). Would this be counted as rate limiting under point [1] or point [2] ? --Regards, Denzil -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth in Twitter via Python
Oh! I should avoid creating multiple user accounts in that case. I would like to perform analysis on a target set of users and not streams. How do I proceed? I should add that 350 requests per hour is highly insufficient for my use case. --Regards, Denzil On Sat, Jun 4, 2011 at 11:33 PM, Tom van der Woerdt i...@tvdw.eu wrote: I'd like to point out that this is against the TOS. You should limit your API requests where possible - for a normal application with user interaction you won't need more than 350 per hour. If you do some sort of data analysis, you may need to use streams instead. Tom On 6/4/11 7:53 PM, Correa Denzil wrote: Tom : Thanks. I will create multiple user accounts. I guess about 20 (350 * 20 = 7000 considering 1 request per second) should solve my issue. --Regards, Denzil On Sat, Jun 4, 2011 at 3:35 AM, Tom van der Woerdti...@tvdw.eu wrote: If you authenticate, all requests (except for search) will go into the 350 requests. If you want 500, then perform 150 unauthenticated and 350 authenticated. If you need even more, use more accounts to do the requests. Tom On 6/3/11 11:06 PM, Correa Denzil wrote: Ah! I feel similar. Which essentially means that despite acquiring data which is publicly available I will be limited to 150 requests per hour and even OAuth will not help increasing it to 350 ? --Regards, Denzil On Sat, Jun 4, 2011 at 2:32 AM, James Giffordja...@jamesrgifford.com wrote: The way I'm reading it it falls under 1. But I might be mistaken. --James Gifford http://jamesrgifford.com On Jun 3, 2011, at 17:01, Correa Denzilmcen...@gmail.com wrote: Hi, I am collecting Twitter data for my research. The API says that : [1] Anonymous calls are based on the IP of the host and are permitted 150 requests per hour. This classification includes unauthenticated requests (such as RSS feeds), and authenticated requests to resources that do not require authentication. [2] OAuth calls are permitted 350 requests per hour. I want to seek a clarification on point [1]. Lets say I want to access a list of followers of a user id (which is public). Would this be counted as rate limiting under point [1] or point [2] ? --Regards, Denzil -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] One access token for OAuth using Twitter API
Hi, I would like to use a one access token with OAuth to make calls to the Twitter API. I am NOT trying to build a web application but rather trying to harvest data from Twitter to perform some analysis. I would like to collect three types of data : followers, friends and user information including status updates as available. I am able to do all the same using no authentication as the data I collect are from public users only. However, due to API limits I would like to shift to Oauth which would allow me to get access to 350 requests per hour. Is OAuth one access token the right approach for my task? Is there any documentation or example to do the same? I am not using any wrapper. Wrappers like Python-Twitter and Twython don't allow functions to access followers, status updates of other users i.e. users with data publicly available. I use urllib2 to directly call the URL as given on the Twitter API documentation website. I have registered an application and have all the keys (API key, Consumer Key, Consumer Secret, Access Token, Access Secret Key) with me. I would just like to get myself authenticated and mine Twitter to collect data. Programming Language : Python --Regards, Denzil -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] One access token for OAuth using Twitter API
Scott : Thanks, but I seem to be lost for ideas as to how to perform an OAuth in this case. Is there any example, code, documentation I can look into to explain the phenomena? --Regards, Denzil On Sun, Jun 5, 2011 at 1:37 AM, Scott Wilcox sc...@dor.ky wrote: Yes, the 'My Access Token' would suit that use case. On 4 Jun 2011, at 20:57, Correa Denzil wrote: Hi, I would like to use a one access token with OAuth to make calls to the Twitter API. I am NOT trying to build a web application but rather trying to harvest data from Twitter to perform some analysis. I would like to collect three types of data : followers, friends and user information including status updates as available. I am able to do all the same using no authentication as the data I collect are from public users only. However, due to API limits I would like to shift to Oauth which would allow me to get access to 350 requests per hour. Is OAuth one access token the right approach for my task? Is there any documentation or example to do the same? I am not using any wrapper. Wrappers like Python-Twitter and Twython don't allow functions to access followers, status updates of other users i.e. users with data publicly available. I use urllib2 to directly call the URL as given on the Twitter API documentation website. I have registered an application and have all the keys (API key, Consumer Key, Consumer Secret, Access Token, Access Secret Key) with me. I would just like to get myself authenticated and mine Twitter to collect data. Programming Language : Python --Regards, Denzil -- Scott Wilcox @dordotky | sc...@dor.ky | http://dor.ky +44 (0) 7538 842418 | +1 (646) 827-0580 -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth in Twitter via Python
Tom : I probably missed the point. I see the targeted users, their data is public and accessible using no authentication but the API limits are too small. I can't gain OAuth access from them. I would like to increase this to more API calls using OAuth. --Regards, Denzil On Sun, Jun 5, 2011 at 1:41 AM, Tom van der Woerdt i...@tvdw.eu wrote: easily -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Oauth in Twitter via Python
Hi, I am collecting Twitter data for my research. The API says that : [1] Anonymous calls are based on the IP of the host and are permitted 150 requests per hour. This classification includes unauthenticated requests (such as RSS feeds), and authenticated requests to resources that do not require authentication. [2] OAuth calls are permitted 350 requests per hour. I want to seek a clarification on point [1]. Lets say I want to access a list of followers of a user id (which is public). Would this be counted as rate limiting under point [1] or point [2] ? --Regards, Denzil -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Oauth in Twitter via Python
Ah! I feel similar. Which essentially means that despite acquiring data which is publicly available I will be limited to 150 requests per hour and even OAuth will not help increasing it to 350 ? --Regards, Denzil On Sat, Jun 4, 2011 at 2:32 AM, James Gifford ja...@jamesrgifford.com wrote: The way I'm reading it it falls under 1. But I might be mistaken. --James Gifford http://jamesrgifford.com On Jun 3, 2011, at 17:01, Correa Denzil mcen...@gmail.com wrote: Hi, I am collecting Twitter data for my research. The API says that : [1] Anonymous calls are based on the IP of the host and are permitted 150 requests per hour. This classification includes unauthenticated requests (such as RSS feeds), and authenticated requests to resources that do not require authentication. [2] OAuth calls are permitted 350 requests per hour. I want to seek a clarification on point [1]. Lets say I want to access a list of followers of a user id (which is public). Would this be counted as rate limiting under point [1] or point [2] ? --Regards, Denzil -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
[twitter-dev] Pagination using cursors to retrieve follower ID's
Hi all, The Twitter API mentions that in order to retrieve more than 5000 user followers one must set the cursor = -1 and use the next_cursor_str and previous_cursor_str options to paginate over the results. However, I observe that I am retrieved similar results(follower ids) on each pagination call. The API suggests that Querying without the cursor parameter is deprecated and should be avoided. https://dev.twitter.com/doc/get/followers/ids --Regards, Denzil -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Pagination using cursors to retrieve follower ID's
Taylor : Thanks for the response. I make the calls in JSON. Here's how I make the calls. The first call is for : https://api.twitter.com/1/followers/ids.json?screen_name=evcursor=-1 This call returns with next_cursor_str:1370145116766924316 I make the next cursor call as : https://api.twitter.com/1/followers/ids.json?screen_name=evcursor=-1next_cursor=1370145116766924316 Is this correct? If that's the case, each of these calls return a 'ids' list which consist of the list of followers (5000 per call). I see that the ids are overlapping on each call which shouldn't happen ideally. --Regards, Denzil On Fri, Jun 3, 2011 at 2:06 AM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Correa, I can't reproduce this issue -- can you share which account you're using to test this? Is it an account with more than 5000 followers? For example, I tried making these requests for @ev, who has 1.3M+ followers. The first request with cursor=-1 begins with 309873322 and ends with 107800155. The second request with cursor=1370144140325967611 begins with 307280112 and ends with 301233284 Make sure that you're using cursor_str instead of cursor from the response of these methods if you're making the requests in languages like Javascript where the act of consuming the Integer representation truncates/malforms the integer. Malformed cursors may be the cause of your duplicated data. @episod - Taylor Singletary On Thu, Jun 2, 2011 at 1:11 PM, Correa Denzil mcen...@gmail.com wrote: Hi all, The Twitter API mentions that in order to retrieve more than 5000 user followers one must set the cursor = -1 and use the next_cursor_str and previous_cursor_str options to paginate over the results. However, I observe that I am retrieved similar results(follower ids) on each pagination call. The API suggests that Querying without the cursor parameter is deprecated and should be avoided. https://dev.twitter.com/doc/get/followers/ids --Regards, Denzil -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Pagination using cursors to retrieve follower ID's
Taylor : Thanks for the response. Ah! I should've realized this 6 hours earlier. Thanks for the help :-) --Regards, Denzil On Fri, Jun 3, 2011 at 2:30 AM, Taylor Singletary taylorsinglet...@twitter.com wrote: You've almost got it right -- in your second request, your params should include cursor=1370145116766924316 -- cursor=-1 needn't be included, as -1 is the value for cursor in the first step, and then you adjust cursor for each subsequent request. The response tells you what your next cursor= value should be, not the name of key/value pair to include. So step 1: https://api.twitter.com/1/followers/ids.json?screen_name=evcursor=-1 And step 2: https://api.twitter.com/1/followers/ids.json?screen_name=evcursor=1370145116766924316 And so on. @episod - Taylor Singletary On Thu, Jun 2, 2011 at 1:53 PM, Correa Denzil mcen...@gmail.com wrote: Taylor : Thanks for the response. I make the calls in JSON. Here's how I make the calls. The first call is for : https://api.twitter.com/1/followers/ids.json?screen_name=evcursor=-1 This call returns with next_cursor_str:1370145116766924316 I make the next cursor call as : https://api.twitter.com/1/followers/ids.json?screen_name=evcursor=-1next_cursor=1370145116766924316 Is this correct? If that's the case, each of these calls return a 'ids' list which consist of the list of followers (5000 per call). I see that the ids are overlapping on each call which shouldn't happen ideally. --Regards, Denzil On Fri, Jun 3, 2011 at 2:06 AM, Taylor Singletary taylorsinglet...@twitter.com wrote: Hi Correa, I can't reproduce this issue -- can you share which account you're using to test this? Is it an account with more than 5000 followers? For example, I tried making these requests for @ev, who has 1.3M+ followers. The first request with cursor=-1 begins with 309873322 and ends with 107800155. The second request with cursor=1370144140325967611 begins with 307280112 and ends with 301233284 Make sure that you're using cursor_str instead of cursor from the response of these methods if you're making the requests in languages like Javascript where the act of consuming the Integer representation truncates/malforms the integer. Malformed cursors may be the cause of your duplicated data. @episod - Taylor Singletary On Thu, Jun 2, 2011 at 1:11 PM, Correa Denzil mcen...@gmail.com wrote: Hi all, The Twitter API mentions that in order to retrieve more than 5000 user followers one must set the cursor = -1 and use the next_cursor_str and previous_cursor_str options to paginate over the results. However, I observe that I am retrieved similar results(follower ids) on each pagination call. The API suggests that Querying without the cursor parameter is deprecated and should be avoided. https://dev.twitter.com/doc/get/followers/ids --Regards, Denzil -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
