I'm using a twitter API to fetch latest tweets from some person.
It was working well until 16 June 2013.
But now it gives me error - "410 error - rest api v1 not active" while fetching tweets.
Can anyone please help me out to migrate api version 1.1 over 1.0?
or
any other solution
Thanks
I never worked with twitter http api directly. If your twitter codebase is small then you can refactor your code by using a library or implementing some kind of abstraction to make migration to later minor API changes less painful.
As I can see from this article migration seems pretty straightforward. You should always authenticate your requests for all API calls.
API v1 was retired recently, as outlined here. To get up and running again, look at the changes from 1.0 to 1.1 here or here.
Related
I was trying to use OpenUI5 with a .NET OData v4 Web API service. It looks like the client embeds the "Max OData Service Version" header with the HTTP request by default and my service doesn't like that. Additionally, documentation notes support for v2 experimental v3.
Does anyone know when support for v4 is expected?
Thanks so much!
There are people working on the v4 support, but don't expect it to be available in the next few months.
Currently a new version of the v2 model is being implemented that has performance optimizations and better batch support, after that one is finished I guess the v4 support will be an important part of the agenda.
OData V4 finaly just got released.
https://sapui5.netweaver.ondemand.com/sdk#docs/api/symbols/sap.ui.model.odata.v4.ODataModel.html
But keep in mind what Jens Ittel said:
[...] Due to its limited feature scope, we will not recommend to use
the first of these releases of the model implementation for productive
usage. [...]
So I'm using Ocotopress 2 and love it. However, I think the twitter plugin may have been broken for a while before I noticed.
I suspect it's because it uses the now retired v1.0 twitter API.
I get
Failed to load resource: the server responded with a status of 410 (Gone)
for the URL
https://api.twitter.com/1/statuses/user_timeline...
Can anyone confirm that and suggest a fix? I can't/don't want to upgrade the Octopress 3 so I'm hoping there's an easy fix.
Yes, Twitter API v1.1 requires authentication so Octopress dropped it (see the issue on Github).
For a fix, I'm using a method described in this pull request which involves creating a Twitter timeline widget and adding the widget ID to _config.yml. Easy to setup and has worked quite well for my basic needs.
There used to be a YouTube api console for v2 that allowed generation of v2 api keys. Mentioned here by Jeff Posnick. I get a 404 error now.
I know that v2 has been deprecated but it takes time to switch to the new v3 version and we should be still be able to use v2 until the end date of April 2015. Does anyone know where to get v2 api keys?
At the bottom of the post you reference, Jeff mentioned that one goal is to make the old v2 API aware of new keys generated via the API console (now the cloud console). I just tested it and it seems to work now to use a "key for browser applications" for deprecated v2 calls as well as the read-only v3 API calls, but someone else may be able to comment if this is, in fact, accurate.
I've started to read something about certain Twitter API 1.0 deprecation deadline around march 2013, inviting all their users to migrate onto the 1.1 version of said API. The main difference between the 2 of them (among others) seems to be "the OAUTH thing".
Currently, I've been developing an iOS/Android app, which uses the search.twitter.com/search.json API with no major issues.
The nice thing is that "search.twitter.com" API is an unauthenticated one, and for now, it's more than enough for my needs. I "don't currently want to invest time" onto the OAUTH authentication right now.
On the other hand, and to be honest, I have no idea if the "search.twitter.com" API is the same thing as the 1.0 Twitter API. Is it? Have I been using Twitter API 1.0 without knowing it?
Does anyone know for sure if the search.twitter.com "API" is going to become "also" deprecated on March 2013?
Thanks!!
Finally, it looks like this API will be deprecated.
You can find more information on Twitter developers forum.
https://dev.twitter.com/discussions/12727
https://dev.twitter.com/discussions/14587
https://dev.twitter.com/discussions/14785
So it's time to move 1.1 and OAuth.
I'm using related_results to show a conversation thread in a website application.
I want to migrate the api version to 1.1 but this function is not implemented.
Somebody know how it do that?
Thank you mates!
Official answer from Twitter is that no such feature will make it to API 1.1 :(
https://dev.twitter.com/discussions/11292