API v1 Retirement Discussion

LeeGenerale · 2013-04-17T17:10:49.000Z

Great. Thanks. That’s what I needed to know.

lphilps · 2013-04-17T19:19:20.000Z

I’m joining this conversation late, but I think I might know what the problem is.

If your application was created as a “read-only” app, it will work with search but fail with a 401 when using the streaming API. You need to have a read/write application to use stream.twitter.com/1.1/statuses/filter.json if I recall correctly.

Hope that helps.

sonal_4am · 2013-04-18T11:30:20.000Z

Rate limit on V1.1 is IP based or not?

sonal_4am · 2013-04-18T11:32:43.000Z

How can I do more then 180 searches with in 15 min.

episod · 2013-04-18T14:37:03.000Z

IP address is not factored in to any API v1.1 rate limiting, take a look at the documentation: [node:10066]

episod · 2013-04-18T14:37:36.000Z

Unfortunately it’s not possible. Your best bet would be to go through the libraries that you use and verify that they’re using API v1.1.

episod · 2013-04-18T14:38:16.000Z

Consider using [node:13439].

Miles4Charity · 2013-04-18T23:24:36.000Z

Hi, Our app has stopped logging in to Twitter and we haven’t done thee REST API update yet and our users are getting issues. WHy won’t it work after the blackout please?

We get “There was a problem requesting authorisation from Twitter” on a Request Error. Any help appreciated to get us back on line please? Has the blackout affect the app settings in anyway?

episod · 2013-04-19T14:46:48.000Z

There have been a number of security corrections to OAuth in the past few weeks – review this thread to make sure you’re all up to date: [node:16443].

MimiOwens2 · 2013-04-22T16:57:54.000Z

How can I test to be sure tweets are working ok on my site with the new api?

episod · 2013-04-23T14:34:54.000Z

Make sure you’re using the right paths. You should be in the driver’s seat as to whether you’re making requests to API v1 or to API v1.1. If you’ve already migrated to API v1.1 and want to make sure that you’re approaching the stricter auth and HTTP requirements correctly, consider trying to send tweets, direct messages, and execute search queries with varying characters and punctuations to sniff out any corner cases where you may be invalidly encoding strings.

adrian86438935 · 2013-04-30T10:19:00.000Z

The TwitterOauth PHP library is listed as working with Twitter 1.1 but only on some calls. statuses/user_timeline does not work on credentials which are fine for search/tweets and account/verify_credentials

It would be a lot better if Twitter supplied a PHP library in the way Facebook does instead of relying on private libraries which are not reliable

episod · 2013-05-03T17:13:50.000Z

We’re extending the retirement date of API v1 to June 11, 2013. See [node:17327] for more information.

MehulJoisar · 2013-05-04T06:32:00.000Z

Hi,
I am using following api to get public tweets by using “screen_name” without doing any authentication,

https://api.twitter.com/1/statuses/user_timeline.json?include_rts=true&screen_name=mehuljoisar&count=50

will it work as expected after retirement of api v1 on 16th June 2013 ?

quadhome · 2013-05-06T03:44:19.000Z

Will there be any anonymous access to twitter feeds after the v1 API is deprecated?

fr3nd · 2013-05-06T13:12:00.000Z

Will https://twitter.com/users/show/username keep working?

episod · 2013-05-06T14:22:21.000Z

This request will indeed cease to function after API v1 is retired. (note the “/1/” in the URL)

episod · 2013-05-06T14:23:40.000Z

Anonymous as in not requiring an end-user be identified – yes, you can use [node:13439] to make such requests to most methods.

Anonymous as in not requiring the application making the request to be identified – no.

episod · 2013-05-06T14:24:22.000Z

It will not – this method is also technically not part of the documented API.

nschonni · 2013-05-06T15:05:00.000Z

We have an WCAG/Accessibility blocker for moving to the new widget. Could someone please review https://dev.twitter.com/issues/1009