API v1 Retirement Discussion

OVNieuwsNL · 2013-06-16T12:16:44.000Z

How do i fix my twitter widget, it gives a bad request. Can anyone send me the good one??

´´GET https://api.twitter.com/1.1/search/tweets.json?q=from:SporenNetNL&callback=TweetTick&rpp=50 400 (Bad Request) ´´

ESpacey · 2013-06-16T13:42:58.000Z

I have made an example in PHP of how to use the API 1.1, notably the project examples that where distributed for v1. haven’t been updated for v1.1, notably also the PHP Libraries looks like they are abandoned.

To Download the Package of PHP files for the Twitter v1.1 API Example and link to it on your pages please twitter these links are permanent:

Download: https://sourceforge.net/p/eoops/code/HEAD/tarball?path=/Example%20Script/Twitter%20oAuth%20Example
Code: https://sourceforge.net/p/eoops/code/HEAD/tree/Example%20Script/Twitter%20oAuth%20Example/
Wiki: https://sourceforge.net/p/eoops/wiki/Twitter%20oAuth%20Example/

lsces · 2013-06-17T02:23:49.000Z

Sorry - but I have JUST hit this problem with a number of customer sites and I think that who ever though up this idea needs taking out and shooting !!!
Since many of my customers are not very computer literate, the ONLY way to get their twitter feeds back up is to ask them for their password to their twitter account so I can go in and create the necessary ID to get their website feeds working again. Did NOBODY think that requiring that was going to be a result of this change ???

AdryGese · 2013-06-17T14:26:08.000Z

Hello,
like many other web designers I have this problem:

Appeared on my page my last 2 tweets using the following code:
“https://api.twitter.com/1/statuses/user_timeline/USERNAME.json?callback=twitterCallback2&count=2” using the style of my page and not that horrible theme twitter;

But if I update the link:
https://api.twitter.com/1.1/statuses/user_timeline/USERNAME.json?callback=twitterCallback2&count=2 "
https://twitter.com/1.1/statuses/user_timeline/USERNAME.json?callback=twitterCallback2&count=2 "
http://api.twitter.com/1.1/statuses/user_timeline/USERNAME.json?callback=twitterCallback2&count=2 "
http://twitter.com/1.1/statuses/user_timeline/USERNAME.json?callback=twitterCallback2&count=2 "

I get this error:
error: {“errors”: [{“message”: “Bad date Authentication”, “code”: 215}]}

Looking around I have not found a solution to get my last 2 tweets on my site, I do not think too much to ask?

It was not at all nice and cute by Twitter API 1 block and insert the 1.1 API without even a detailed guide on how to get back to work with the API, millions of web designers have the same problem …

ncttest1 · 2013-06-17T14:41:56.000Z

without twitter authentication how can i fetch twitter userid and screen name

because in old api its working fine for over site demo link.

please help me for solve this issue.

NoorulT · 2013-06-19T01:18:42.000Z

Mr Singletary, I’ve been told that it’s possible to subscribe to a Twitter feed in RSS form by entering the username here to generate a link: http://www.twitter-rss.com/

I understand that one could subscribe to your Twitter feed, for instance, with this link: http://www.twitter-rss.com/user_timeline.php?screen_name=episod

I’m not sure if it works but would be interested to know your thoughts.

InamdarNagama · 2013-06-20T05:07:08.000Z

I have one question regarding the migration from api v1 to v1.1.
I am using openid script for user registration using twitter.Now it has stopped responding due to api up-gradation.
Now I want to know know the exact way of upgrading the twitter API.as I explored alot couldn’t find the guiding link.

c_r_w · 2013-06-25T17:50:31.000Z

Exactly right, thanks!

c_r_w · 2013-06-25T17:53:34.000Z

The original post in this thread has a great, detailed overview on how to move to v1.1: https://dev.twitter.com/discussions/10644

c_r_w · 2013-06-25T17:57:38.000Z

As a result of the new requirements that API requests be signed with OAuth, it is no longer possible to have a pure client-side app that also keeps your secret keys secret. You will need to write a server-side proxy to make the requests between your client-side app and Twitter.

c_r_w · 2013-06-25T17:59:59.000Z

Yes indeed: [node:3726]. OAuth is fairly complicated, and will require some programming knowledge. You might also be interested in our options for websites, found here: https://dev.twitter.com/docs/twitter-for-websites

mgokhanbakal · 2013-06-29T19:01:11.000Z

I always receive the error message that is “{“errors”:[{“message”:“Bad Authentication data”,“code”:215}]}” when I request the link which is “https://api.twitter.com/1.1/search/tweets.json?q=%40twitterapi&count=10”.

Can someone help me on this?

Thanks.

CEDCANDE · 2013-07-01T12:01:42.000Z

Why can you not simply keep the old API? It was working well for us until it was disabled and the new API does not work as the old one did. This is causing a consternation of problems for us.

IAGSDC · 2013-07-01T21:40:40.000Z

We don’t have any developers - we are a non-profit. But we used the old widget for a long time, and users liked it. When the old one stopped working, we generated the new code at the widget page for a timeline widget, and dropped the code in just as it was in the widget page. It doesn’t do anything, and none of us understand any of it We seem to be completely stuck. We have a test page with the just the widget code at http://iagsdc.info/test/widget.php. All it brings up is the link. We really don’t know who to ask - I’ve looked around on this site, but clearly everyone here is much more technical than we are. Is there any hope of getting a simple widget again, like the old one? Here’s our generated code for the test page, if that helps:

Untitled Document Tweets by @IAGSDC

bipin52165 · 2013-07-02T07:49:01.000Z

In API v1.1, there is a problem in retweet API. I tried by web intent and its working fine but using with API its not working for me. Is there anything missing by me or you can check it? Please replay me ASAP.

abraham · 2013-07-02T16:03:33.000Z

What is the problem you are seeing? It doesn’t look like the retweet method changed between v1 and v1.1.

https://dev.twitter.com/docs/api/1.1/post/statuses/retweet/%3Aid

abraham · 2013-07-02T16:05:25.000Z

It looks like you got the new widget working as expected on your landing page.

c_r_w · 2013-07-02T17:33:38.000Z

This code looks like it is intended to run client-side in a browser. With the change to REST API v1.1, you can no longer run purely in a browser due to the new OAuth v1.0a requirements. You will need to run a proxy that handles the OAuth signing. Please see [node:3726] for all of the details.

theochry · 2013-07-03T07:44:48.000Z

I am working on a project that uses Streaming API with Phirehose library and i can’t download public tweets with sample anymore. Keep in mind that i’m using API v 1.1 ( const URL_BASE = ‘https://stream.twitter.com/1.1/statuses/’; ) what happend? Could anyone help me with this issue please?

Thanks in advance

matrixrunner7 · 2013-07-07T15:21:11.000Z

I was using this URL to get recommended users before 1.1:
https://api.twitter.com/1.1/users/recommendations?connections=true&disabled=true&dismissable=false&display_location=wtf-component&emptyTimelineModule=true&excluded=&followingCount=2&initialResults=true&limit=3&pc=true&scribeContext[component]=user_recommendations

Then, I tried to use the “new” version to get suggested users instead of recommended users:
https://api.twitter.com/1.1/users/suggestions/twitter.json

However, with the new version, I get the following error:
{“errors”:[{“message”:“Bad Authentication data”,“code”:215}]}

I haven’t changed the authentication process from the previous version.
I am running this URL to authorize:
https://api.twitter.com/oauth/authorize?oauth_token=n6DRG7x4QKwo927qtENAqQWunGVjLB6xcukydTgin8

Any suggestions or samples on how to get this working?