How to migrate API v1.1


#1

Migrate API v1.1


#2

Can someone help me please. Getting error Code 410.
The Twitter REST API v1 is no longer active. Please migrate to API v1.1

But how to migrate?


#3

Please help me. Getting error Code 410.
The Twitter REST API v1 is no longer active. Please migrate to API v1.1
But how to migrate? I couldn’t post twitpic anymore :frowning:


#4

Hello, Sir.
I have a same problem in my iOS application.
So I changed “Twitter_Domain” to “api.twitter.com/1.1” in MGTwitterEngine.m
So I can fix 410 error, but I encountered 404 error.
What’s wrong?
How can I do?
Why api often change? why???


#5

My API down, Hotot down, Gwibber down…
Currently I need to go to the Twitter web site to read messages and there is absolute NO explanation how to migrate from 1.0 to 1.1
Also noticed that old documentation for 1.0 still is everywhere and that makes it even more confusing.

At least clean up the old documentation from 1.0 if this version is shut down if it’s not possible to explain how to update.


#6

I am also having trouble trying to figure out how to upgrade my APIv1 for a client. My error is currently:
–failed to open stream: HTTP request failed! HTTP/1.0 410–
I’ve tried different ways of upgrading it but I cannot figure it out to save my life. All I’m finding is documentation on the new API but nothing that explains how to upgrade.


#7

The upgrade process is different for everyone. It’s best to look at how you’re using the API today and compare that to the documentation for API v1.1. Some API methods have changed paths. Some no longer exist. There are also newer ones. All requests require a form authentication, for which you can either use [node:3062] or [node:13439]. There are docs for these topics throughout this site, but admittedly they speak mostly to programmers.

App-only auth is the easiest way to use auth with the API. It barely requires programming anything to get up and running with it.

For some developers, it really is as easy as changing paths they’re using from /1/ to /1.1/. For other developers, you’re going to be learning about authentication for the first time. You may find that things you were able to do in the past aren’t possible anymore – or at least aren’t possible in the context that you’re trying to do them.

We have a lot of aspects to the platform: a REST API, Web Intents, Embedded Timelines, Embedded Tweets, a series of Streaming APIs… explore the options available to you. Some things require you to embrace a few of these.

If you’re just trying to get tweets on a website, Embedded Timelines are really the best bet. If you want to do something more custom or complex, explore [node:126] for a library in your preferred language.

Finally, if you already have an API-based integration with OAuth and are moving to API v1.1, keep in mind that API v1.1 is much stricter from the perspective of HTTP 1.1 and OAuth 1.0A spec compliance. We require all reserved characters to be encoded correctly. Most non-alphanumeric characters are reserved. Many libraries, including some core libraries, perform some of this encoding incorrectly. See http://www.ietf.org/rfc/rfc3986.txt


#8

Thanks Taylor.

But Sir, I changed all 1 to 1.1 in my source already.
But It appears 404 error.

Please give me updated MGTwitterEngine source.
Please


#9

I’ve also changed paths to 1.1but I can’t get methods like statuses/update run. I’m actually s1ck of Twitter explaining all this painful topic generally instead of seriously putting hands on it. This migration just means headaches for developers.

Mr. @episod, I provided an entry full of details and I’m still waiting for a proper answer (https://dev.twitter.com/discussions/18644)

Since the method followers/ids (GET) works OK for me, why doesn’t statuses/update (POST)?


#10

Great Answer.


#11

I have Developed Window Application Which was Doing Lot With twitter.How Can I Do Now.its Giving me this Error The Twitter REST API v1 is no longer active. Please migrate to API v1.1. https://dev.twitter.com/docs/api/1.1/overview
What Should I do Please help.Will I have to Change all my Code


#12

Right Now I am Using Twitterizer2 DLL for My Twitter Software. Now it Stopped Working and Giving me Error
The Twitter REST API v1 is no longer active. Please migrate to API v1.1. https://dev.twitter.com/docs/api/1.1/overview

How Could I Again Use My Software And What Will I have to do.How Could I Migrate My Twitter API


#13

Hello I just want to tweet from a textbox in my website. I did this perfectly using .Net but now 401 “Gone”… The libraries like twitterizer are no longer working and the ones you recoomend are not working with api v1.1 they all say 401 Gone even in their very demo pages! pls take a look at what al we are saying


#14

error verifying credentials: The Twitter REST API v1 is no longer active. Please migrate to API v1.1. https://dev.twitter.com/docs/api/1.1/overview. - trying to use twitter protocol , and status.net twitter protocol. neither works. HELP US OR WE WILL DIE.


#15

just try this url : https://api.twitter.com/1.1/


#16

Dear Sir, do you update MGTwitterEngine.m for fixing 404 error ? Please tell me how to fix this error!!! Thanks!!


#17

hello how can i migrate from V1 to V1.1. Where should i change it please help me…is changes should
done in code or anyother place…


#18

See the top answer by @episod. Just changing the path from /1 to /1.1 is not sufficient, you need to implement OAuth for requests. For the simplest way to do so, see [node: 13439] if you don’t need user context.


#19

Same Problem here


#20

I’m just trying to obtain Application-only authentication. I was told to use the oauth_token and oauth_token_secret returned from the
oauth/access_token call instead of the one in your app’s settings in dev.twitter.com.

How???