API v1 Retirement Discussion

Evolve24Dev · 2013-04-16T20:05:16.000Z

I can tell you what oauth token and secret we are using and what consumer key and secret we are using. I’m not sure what you mean by account. We make a request to the 1.1 streaming URL and then sign it with our oauth token. There isn’t an account, is there?

episod · 2013-04-16T20:08:13.000Z

The access token/oauth_token represents an account – accounts connect to streaming either through basic auth or through an OAuth 1.0A application. The @username of the account you use to connect or the user ID is sufficient – I can figure out the account from the oauth_token alone.

Evolve24Dev · 2013-04-16T20:11:31.000Z

the oauth token is 109087735-a8iG65xmcuqZiaGJdkwwfKPZm34QzdLWBtW1tHfw Let me know if you need anything else and thank you for your help.

episod · 2013-04-16T20:25:02.000Z

Thanks. I would verify that you (or someone in your organization) haven’t inadvertently revoked the access token you use to connect – either by revoking the application from twitter.com/settings/applications while logged in as the account, denying access through the OAuth handshake process in oauth/authorize or oauth/authenticate, and/or regenerating your access token through the “my access token” feature on dev.twitter.com/apps.

Check if you can use the access token for other operations like https://api.twitter.com/1.1/account/verify_credentials.json which verifies that your credentials and OAuth setup are capable of making valid requests.

Evolve24Dev · 2013-04-16T20:42:23.000Z

Ok thank you, we are checking into that now.

LeeGenerale · 2013-04-16T20:42:31.000Z

Have no idea what anyone is talking about. All I do know is I can’t log on to
my account. Please tell me this will all come out in the wash without me having
to jump through hoops.

Evolve24Dev · 2013-04-16T21:04:46.000Z

I created a new token 109087735-a8iG65xmcuqZiaGJdkwwfKPZm34QzdLWBtW1tHfw and we are still getting a 401 error. Any ideas now?

episod · 2013-04-16T21:12:58.000Z

I unfortunately don’t have the ability to see the exact reason you’re getting a 401 here. Did you utilize the OAuth flow to generate your new access token or did you use a different approach? Does that access token work against the REST API? Since you belong to an elevated role, you can temporarily mitigate your issues by using basic auth to connect for the time being while you dig into any other OAuth issues you may have.

When was your last successful reconnection to stream.twitter.com? Are your server clocks in sync with ours? (See the Date header we return in responses).

episod · 2013-04-16T21:18:25.000Z

If you’re having trouble signing in to your account, your best bet would be to let @support know on support.twitter.com/forms – we can’t help here with account issues, sorry.

Evolve24Dev · 2013-04-16T21:22:11.000Z

I used the My Application page here to create a new Access Token. This is the same process that I followed to create the Access Tokens for the Search API which are working.

Migrating my code to basic auth means reprogramming so that is out of the question.

Our last successful call to the Streaming API with the old token was at 2:11:36pm Central today. Then at 2:11:44pm Centry it started failing.

episod · 2013-04-16T21:35:44.000Z

What’s the exact error response you’re getting? How often do you typically reconnect? To rule out issues with OAuth versus something intrinsic to your account, I would really recommend trying to connect using curl on the command line and basic auth. I’m not seeing any systemic issues with OAuth right now, nor anything specific about your account that would prevent you from connecting. Have you checked your server clock?

Evolve24Dev · 2013-04-16T21:45:15.000Z

Thank you.

What I see in my log file is [log4j] [2013-04-16 14:31:08,532] com.maritz.evolve24.loader.twitterloader.TwitterRetriever INFO Server responded 401

If I am reading the code right we reconnect every hour, and we checked the time on the server and it is correct.

I’m a Java programmer not a UNIX guy so I don’t know how to use CURL. I’ll research that.

In the meantime, one question for you is, what do I use for authentication with basic auth? Other than my developer account which I logged in here with, all I know is our oauth tokens.

episod · 2013-04-16T21:56:10.000Z

Interesting. We recommend in the documentation not to reconnect on fixed schedules – your connections should really strive to be maintained on the order of days and weeks.

On your server, you can likely execute a command like this:

curl --verbose “https://stream.twitter.com/1.1/statuses/sample.json” -u screen_name:password

The user you are connecting with is “e24it”

Evolve24Dev · 2013-04-16T21:59:27.000Z

I took the access token and used it in a call to the search API and it worked fine. I then changed my test program to call the streaming API and I got this error:

Error 401 Unauthorized

HTTP ERROR: 401

Problem accessing '/1.1/statuses/filter.json'. Reason:

    Unauthorized

Why would this work with the search API but fail with the streaming?

episod · 2013-04-16T22:02:55.000Z

Do you get the same thing on https://stream.twitter.com/1.1/statuses/sample.json ? (That streaming method doesn’t require parameters)

It could be that you have some mis-encoded values in the parameters you’re sending – check what your track terms are if you’re sending them and verify everything is a) UTF-8 and b) percent-encoded properly for HTTP 1.1 and c) your OAuth library is re-encoding that valid HTTP 1.1 percent-encoded data.

Evolve24Dev · 2013-04-16T22:12:20.000Z

When I called api.twitter.com/1.1/search/tweets.json with the oauth token and some query parameters it worked. When I called stream.twitter.com/1.1/statuses/filter.json with a track parameter of glyphosate, I got a 401 error response. There was only 1 track parameter so if I read your response right it should have worked.

episod · 2013-04-16T22:18:41.000Z

Interesting. Let’s take this to email – can you send me an email to episod at twitter dot com and include in it the consumer key you’re using to connect? Thanks!

Evolve24Dev · 2013-04-16T22:24:51.000Z

I just sent the email. Thank you for your help.

magg73883058 · 2013-04-16T23:39:52.000Z

i can´t sing in with oauth you should make a guide with more details please?

weblivz · 2013-04-17T12:59:51.000Z

I’m migrating an app that uses a bunch of libraries to abstract some of the auth and api queries … all of which seem/suggest to have been migrated.

However, when the blackout happened the office was closed it was about 10pm here. I’d like to run a few tests - is it possible to switch off the v1.0 api for a specific app (similar to how the fb graph api works)?