Discussing API v1.1

episod · 2012-10-03T21:06:16.000Z

We will likely support more programmatic manipulation of the new widget platform soon. Stay tuned.

antanova · 2012-10-04T15:45:00.000Z

What would be the best way to pull the latest 5 public tweets from a user? At the moment I’m using

jQuery.getJSON("https://api.twitter.com/1/statuses/user_timeline.json?user_id=XXXXXX&count=5&callback=?");

where it’s only a single specific user whose tweets are being pulled onto a single website.

It seems bizarre that you’d block access to public tweets in this way. As I understand it, now instead of using the above simple code, I must create an application on your platform, then create application logic on my server to use oAuth, then pass that to my front-end.

Is the above correct, or am I missing something simple I should be doing?

BenjaminEWhite · 2012-10-04T21:29:25.000Z

+15 (per 15 minute black of time)…

Just want to echo what’s been said above. I do a good deal of network analysis on Twitter follower and friends networks – the v1.0 general limit of 350 has never given me problems, but if I’m looking at a hard limit of 60 calls per hour for this endpoint, I foresee problems.

BenjaminEWhite · 2012-10-04T21:35:53.000Z

+1

Senhor_H · 2012-10-05T02:46:00.000Z

Im getting some errors while trying to retrieve user mentions in API 1.1… someone know whats happening??

Both https://api.twitter.com/1.1/statuses/mentions_timeline.json and https://api.twitter.com/1.1/statuses/mentions.json returns {“errors”:[{“message”:“Bad Authentication data”,“code”:215}]}

episod · 2012-10-05T14:36:00.000Z

The 1.1 API requires OAuth, which isn’t recommended for pure client-side integrations. It’s not that we’re blocking access to tweets this way, we’re just requiring verifiable application identification which cannot be securely established over client-side Javascript.

Server-to-server communication is best when using the REST API, otherwise using our widgets are also an option.

AccedoNYDev · 2012-10-05T16:50:00.000Z

Thanks for all your clarification on the new API Taylor. One more question to add to the pile:

Our app is currently retrieving oAuth tokens via the “client_auth” setting at this endpoint:
https://api.twitter.com/oauth/access_token
(Our app run on IPTV platforms and so cannot redirect to twitter.com for user login and then follow a return url).

The docs seem to indicate this use-case will continue to work the same on the 1.1 API but the endpoint is unversioned so I don’t seem to have a way to test it before March. Is there a place to test our usage of the new version of the endpoint? Will the behavior of this edgecase usage of this endpoint remain consistent after the switchover?

Thanks.

c0ri · 2012-10-06T17:00:54.000Z

I’d like to see something done about the list method as well. should be able to set a cursor with some variable limit up to 300 or so so we can get a listing of people on a list with only a few calls.

Can someone please address this with the next API update?

Thanks!

Cori

sferik · 2012-10-06T17:49:10.000Z

I just had another thought about how to make this better.

What if GET lists/members was replaced by GET lists/members/ids, which behaved exactly like GET friends/ids and GET followers/ids?

This would allow someone to get the IDs of all the members of a list in a single API call. It would then take as many as 5 (and as few as 1) additional API calls to GET users/lookup to fetch the full user objects, but this shouldn’t be a problem, since this resource already has a higher rate limit (180 requests per rate limit window).

What do you say?

paul · 2012-10-08T10:43:14.000Z

Concerning 5a, grouped tweets. Would it be a violation, if an app enabled a user to copy/paste individual tweets from a rule-conforming timeline to a non-chronological pool of entities, that is then stored on the machine with the users consent? So that the app per se does not interweave a timeline?

antanova · 2012-10-08T12:38:53.000Z

So, there will be no publicly accessible feeds of a user’s recent tweets in any format other than the html at twitter.com/username, is that correct?

In effect that means you are blocking client-side access to tweets. Unless I build a scraper for the html page.

episod · 2012-10-08T14:34:53.000Z

It sounds like you use the “xAuth” form of OAuth.

Our OAuth model remains unchanged by API v1.1 – consider the “version” of the auth model to move independently from that of the API… we continue to allow usage of xAuth on qualified devices in API v1.1 and v1 alike.

episod · 2012-10-08T14:35:32.000Z

I agree that these limits could be more intuitive and productive and am working to get the method revised with better cursoring. Stay tuned.

AccedoNYDev · 2012-10-08T14:53:48.000Z

Great, thank you for the clarification.

jnylund · 2012-10-09T12:04:27.000Z

1, we have the same problem. In order to do social graph analysis we need friend_id’s and follower_ids, the new limits make this impossible.

episod · 2012-10-09T15:31:29.000Z

That does not sound like a display requirements violation to me, though you may want to follow up with API policy to be sure.

todd_michaud · 2012-10-10T13:30:38.000Z

+1 The ability to speed up this graph analysis is very important.

TalkToo_Me · 2012-10-15T07:49:00.000Z

I’m using a PHP library to connect by oAuth to the Twitter API. Currently the library is using these urls:

protected $requestTokenUrl = 'http://twitter.com/oauth/request_token';
protected $accessTokenUrl = 'http://twitter.com/oauth/access_token';
protected $authorizeUrl = 'http://twitter.com/oauth/authorize';
protected $apiUrl = 'http://twitter.com';

Now since the upgrade to api version 1.1 I’m getting following error: ‘Sorry, that page does not exist’ (code 34).

When I change the URL’s to:

protected $requestTokenUrl= 'https://api.twitter.com/oauth/request_token';
protected $accessTokenUrl = 'https://api.twitter.com/oauth/access_token';
protected $authorizeUrl = 'https://api.twitter.com/oauth/authorize';
protected $apiUrl = 'https://api.twitter.com';

I’m getting this error:
[error] => Could not authenticate with OAuth. [request] => /statuses/update.json )

What am I doing wrong?

maxim_demchenko · 2012-10-17T11:27:00.000Z

HI everyone,

In API 1.1 I don`t see similar API to this one from version 1.0

https://dev.twitter.com/docs/api/1/get/statuses/retweeted_of_me

How to get most recent tweets of user that have been retweeted by others in 1.1 API?

Thanks

episod · 2012-10-17T14:47:20.000Z

It’s a longer process currently in API v1.1 but it’s likely that statuses/retweets_of_me will be making a come back.