Discussing API v1.1

meni56 · 2013-05-08T13:03:00.000Z

we have a web app written on Flex that have twitter roll per #hashtag
before this update we did http://search.twitter.com/search.atom?q="+hashtag without ask the clients to register.
Is that way to show twitter roll without log in still available?

thedubjoy · 2013-05-11T02:21:23.000Z

Please increase API rate limit. Thx.

PTadela · 2013-05-11T10:39:48.000Z

Looking at the rate limits for lists, is it true that lists/statuses is in the 15 calls / 15 minute bucket?

I mean that way, you can only fetch tweets for one list per minute on average?

That would severely cripple the lists feature, wouldn’t it? Just imagine you’ve got more than 15 lists …

quenotacom · 2013-05-14T03:00:23.000Z

Hi @episod,

I am having a problem lately, i dont know if is my fault or something changed in api:

I am trying to send a update status with a text like this ‘hello’, and the tweet looks like ‘hello’ (with ampersands) in the timeline. The point is i urlencode once the &status= inside the url, and the tweet is displayed with ’ after that.

Any recommendations, I have some examples without problem, so I dont know if a modification took place recently.

Thxs

episod · 2013-05-13T16:54:08.000Z

lists/statuses was raised to 180 requests per user per 15 minutes a few months ago. It also has a 180 limit for the app-only auth context.

SnookiLala · 2013-05-15T18:56:00.000Z

Solved this problem !
in EpiTwitter.php just change like this:

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/’;

kennylam777 · 2013-05-20T07:13:35.000Z

cool

GPhil82 · 2013-05-23T19:38:00.000Z

Hi,

I was using http://api.twitter.com/1/help/test.json to verify that the Twitter API was running properly before loading my widget. Now, it has been deprecated. What can I use instead for v1.1?

Thank you,

jaysteruk · 2013-06-03T09:04:58.000Z

Hi

We have an app which current uses the old api to return some a limited stream of search results. To make this 1.1 compliant one of the suggestions is to just have the api generate a search url and send the user off to the mobile version of twitter instead of having a bespoke stream. The developers are not clear on whether this would be allowed or not and i’m not sure based on the FAQ’s. Any ideas?

Cheers

episod · 2013-06-03T14:44:23.000Z

Sending a user to the Twitter website should be totally fine, as long as you aren’t re-skinning the content. I would send them more explicitly to twitter.com’s search URLs and let twitter.com decide whether to send a user to mobile.twitter.com or not – the URL schemes of our mobile apps can change without warning while the URL schemes on twitter.com tend to be more stable.

Jinbingl · 2013-06-05T07:31:23.000Z

Hi, I have a couple of questions.

If retweet is set to true, is it possible to find the original tweet user?
Say the followers_count is 20, is it possible to get the user id_str for all 20 users?
Is it possible to obtain more than 15 tweets at once?
Thanks.

guian09 · 2013-06-06T16:52:18.000Z

Hi. I am using https://api.twitter.com/1.1/statuses/home_timeline.json whenever I try to use any parameter like for example
https://api.twitter.com/1.1/statuses/home_timeline.json?count=10
give me this error without any parameter no problem
2 0 7316141533e2c2eb020dad48d3fb1d955b42c197
{“errors”:[{“message”:“Could not authenticate you”,“code”:32}]}
Thanks in advance for your help

zafercalik · 2013-06-07T05:49:30.000Z

is it possible that query with different user base tokens from same ip ? for example i have 100 user base token, and use search api 1.1 with them by order so have an 1800 call per 15 minutes ?

nikhilnarayanan · 2013-06-12T11:15:00.000Z

Getting Tweet count of a URL.

Something like this https://cdn.api.twitter.com/1/urls/count.json?url=http%3A%2F%2Ftechcrunch.com%2F2013%2F06%2F12%2Fgalaxy-s4-zoom%2F&callback=twttr.receiveCount is still working. It uses API v1. Will it stop working soon? What’s the work around with API v1.1? Thanks.

episod · 2013-06-12T14:41:22.000Z

This is not a public API and I wouldn’t rely on it being functional or reliable.

csharpe24 · 2013-06-12T15:05:00.000Z

So does this change mean that an RSS feed is absolutely not possible to pull in XML? I had a working URL that I could plug into my software and have a feed scrolling.

https://api.twitter.com/1/statuses/user_timeline.rss?screen_name=screen_name

Does anyone have an RSS solution for the new version or is this not possible? Thanks in advance!

divine1syllable · 2013-06-12T15:24:00.000Z

Love all the gobbledygook, hate the changes. I just want to continue reading timeline updates of Twitter users I’m following via my Browser Feed Reader on my desktop PC. I was using “http://api.twitter.com/1/statuses/user_timeline/{USERNAME}.rss” to subscribe to the feeds. This obviously no longer functions, but is it still possible to receive Twitter updates via a RSS Feed Reader? If so, can I please get an example of the URL I need to use. If not, that sucks!

episod · 2013-06-12T15:59:03.000Z

Yes, it’s no longer possible to use RSS or XML. Twitter no longer serves RSS, XML, or ATOM response formats.

EricPengXia · 2013-06-12T17:52:00.000Z

Today I have tested the public stream api using JAVA ara.
it works before, but today it always return not authorized, can you figure out.
Even I put the url in the browser:
https://stream.twitter.com/1.1/statuses/sample.json
I can’t sign in.
Can you help me?
Thanks.

Gdamoon · 2013-06-12T18:13:00.000Z

The extension is written in Javascript and currently has the task of monitoring a specified Twitter account’s tweets utilizing Twitter’s rest API version 1.0 to GET new tweets and $parse them.

***What is needed is to upgrade the current rest API 1.0 to twitter’s streaming API 1.1 by authenticating the program using oAuth. Also to use the “follow=UserID” parameter to follow a twitter account so the user can edit the UserID of what account to follow ***

A sample of the code that needs to be altered is located here:

var req = new XMLHttpRequest();

function test() {
req.open(
“GET”, “https://api.twitter.com/1/statuses/user_timeline.json?screen_name=nikestore&count=1550&exclude_replies=true&trim_user=true”,
true);
req.onload = showTweets;
req.send(null);

setTimeout(test, 3000);
}

function showTweets() {
var data = req.responseText;

var tweets = $.parseJSON(data);

The extension also has the script to open specified tweets that match a corresponding ‘keyword’ in a new google chrome tab, but I don’t think that portion of code needs to be altered.