API v1 Retirement Discussion

tanmit · 2013-06-11T22:29:00.000Z

I am using 1.1 API with OAuth tokens. Still I am getting error code 68 - ‘The Twitter REST API v1 will soon stop functioning. Please migrate to API v1.1. https://dev.twitter.com/docs/api/1.1/overview.’, ‘code’: 68
I know that I am using 1.1 API, because when I query for the rates, it returns 180:

limits = api.rate_limit_status()
limits[‘resources’][‘search’][’/search/tweets’][‘remaining’]

IbrahimKoubeiss · 2013-06-11T23:09:59.000Z

can we use the GET statuses/user_timeline without authentication and without creating a twitter application ?

abraham · 2013-06-11T23:13:03.000Z

If you look at the documentation for GET statuses/user_timeline you will see that that it says authentication is required.

https://dev.twitter.com/docs/api/1.1/get/statuses/user_timeline

froginthevalley · 2013-06-11T23:16:19.000Z

The process was completed around 3:30pm (PDT) as testified by @twitterapi.

Thanks everyone! API v1 Retirement is complete. Please use API v1.1 instead. dev.twitter.com/blog/api-v1-is…
— Twitter API (@twitterapi) June 11, 2013

froginthevalley · 2013-06-11T23:18:26.000Z

Are you calling the 1.1 endpoint at https://api.twitter.com/1.1/search/tweets.json?

Docs at https://dev.twitter.com/docs/api/1.1/get/search/tweets.

froginthevalley · 2013-06-11T23:20:10.000Z

As @abraham mentions, all calls must use auth for 1.1, you need to create an application from dev.twitter.com/apps/new. Check [node:13439] for the simplest option.

IbrahimKoubeiss · 2013-06-11T23:24:00.000Z

thanks guys but i’m facing a trouble after creating the application and trying this https://dev.twitter.com/docs/api/1.1/get/statuses/user_timeline my application doesn’t appear in OAuth tool so i can generate a signature
and also if you can please guide me to a tutorial how to get a users timeline using json and jquery, sorry im still a beginner thanks a lot

gregavola · 2013-06-11T23:25:05.000Z

Is there a new Authenticate flow for OAuth here? Is it no longer OAuth Secret + Token to sign? I’m getting 215 Bad Authentication data. Any guidance here?

episod · 2013-06-11T23:28:59.000Z

Are you using an access token and access token secret as well? If you’re trying to do OAuth 1.0A without an access token, we don’t support that flow (and likely your old requests were just considered unauthenticated). Take a look at app-only auth if you want to make API requests without a user context.

gregavola · 2013-06-11T23:31:17.000Z

We already have all the Secret and Token from the user. We were signing the tokens the same way using OAuth. I just changed the end point to 1.1, and now it’s telling me all requests are invalid (Bad Authentication data).

Has the OAuth Signing been changed?

Greg

episod · 2013-06-11T23:47:11.000Z

API v1.1 is considerably stricter about both HTTP and OAuth. Libraries or implementations that make minor errors with either validly formed URLs or POST bodies or OAuth signature base strings will not be able to authenticate. API v1 was much more lenient. Verify that you’re encoding all unreserved characters in your URLs, POST bodies, and signature base strings.

IbrahimKoubeiss · 2013-06-11T23:58:41.000Z

Here’s a good implementation of OAuth and the new api using JQuery and PHP

mikerogers.io

Mike Rogers - Web Developer from Berkshire

A Ruby on Rails developer from the UK's personal website. Showcases an overview of his skills and how to get in touch.

thanks for the support

MajorPowers · 2013-06-12T01:48:00.000Z

Hi. I’m a massive idiot who doesn’t know anything ever. I just love displaying my last tweet on my website where I can control the CSS. How do I alter this code to keep it going?

jwbrown · 2013-06-12T02:40:00.000Z

Here is another implementation of OAuth and the new API. The OAuth connection is similar if not the same as the fullondesign.co.uk implementation previously posted, but this method attempts to cache a copy of the feed locally to increase load time and avoid any call limits if they exists. I apologize in advance for the lack of documentation with it. It is still under development.

https://github.com/jeremyWbrown/php-twitter-feed-api1.1

hope it helps.

salsaindy · 2013-06-12T05:06:23.000Z

Just post the dam php/ruby code for OAuth. TwitterOAuth no longer works.

mavs41bw · 2013-06-12T05:38:55.000Z

CAN SOMEONE PLEASE GUIDE ME ON HOW TO MIGRATE TO API v1.1 ! (Please be detailed)

fbonander · 2013-06-12T07:30:11.000Z

Is there any particular reason this won’t show up in 1.1? The new way feels very much overkill to just get the avatar URL.

Take my application for example, all communication to twitter is executed in the backend and no auth logic in the client. So now I need either to create auth logic in the client or create a backend proxy that redirects to the avatar URL. It’s fine, but I’m curious why a such handy api resource didn’t make the cut to the new api?

norio_nomura · 2013-06-12T08:07:20.000Z

Hi,

Just I know that iOS 6.1.4 Social.framework uses API v1 and iOS built-in Apps can tweet still now.
But some applications which uses iOS 6.1.4 Social.framework fail to tweet.

It seems /1/statuses/update.json response 200 to post from Social.framework with some “application_id” parameter (ex. “application_id=SpringBoard” “application_id=com.apple.mobilesafari”), and response 410 to with another “application_id”.

I hope this will be fix.

Thanks,

kimanisa · 2013-06-12T08:31:31.000Z

Please turn the RSS feeds back on. I have a custom blog written in Rails that I pull my tweets down via RSS and interleave them between blog posts. I can see it now - spending hours debugging environment issues on my local Rails stack trying to integrate whatever gem is needed to access Twitter, and then spending more hours trying to get everything to work in production in a totally different environment. RSS is clean and easy.

LCDyhr · 2013-06-12T09:27:00.000Z

Hi, please help!

I have made a website that fetches tweets from my own account and acts according to these. Somehow this update has sliped by me, but now my website doesn’t work, and I am supposted to present my project for an exam tomorrow. So you can imagine my panic.

I have been using javascript calling: “var twitter_api_url = ‘http://search.twitter.com/search.json’;” and "$.getJSON( twitter_api_url + ‘?callback=?&rpp=5&q=from:’ + twitter_user, function(data) { ". This is not working and I don’t know how to change it. I get error message 410 (gone) and “The Twitter REST API v1 will soon stop functioning. Please migrate to API v1.1. https://dev.twitter.com/docs/api/1.1/overview”. I have tried searching for fixes but I can’t find the correct solution. I think that I might need to make an authentication? But I can’t find a proper guide for this with javascript.

Can someone please help me, thanks?