#1

I have elevated status. I am able to authenticate the v2 api, but NOT able to authenticate the v1.1 api.

I’ve tried many things:

  • Created a new app with new API keys
  • Double-checked all my settings numerous times
  • Checked URL Callback
  • Made sure both v2 and v1.1 APIs are enabled in portal

I’m getting 401 back on https://api.twitter.com/oauth/request_token and the response gives no additional feedback.

#2

What code / implementation are you using? Did it work before? Does it work if you try twurl or something? GitHub - twitter/twurl: OAuth-enabled curl for the Twitter API

#3

It’s worked for years. On the same day I transferred the app over to the new v2 Project area it stopped working.

Is there a diagnostic API call I can make that will give more feedback?

#4

Is the App added as “Production” in the project?

Unfortunately there’s no other endpoint to debug, apart from maybe GET account/verify_credentials | Docs | Twitter Developer Platform but this assumes you already have tokens, which doesn’t help you since you’re getting errors at authentication.

#5

Yes, I set the original app to Production and also the second test app when I tried that. I’m back on the original app and have reset that to Production. I’ve tried every settings permutation I can think of.

I even went back to test code from a month ago that was definitely working and that now fails at request token. Since the only thing different in this test case is the move to the V2 portal, I have to believe the problem lies there.

1 Like
#6

Since this move to the V2 portal has broken my production app, and access tokens only last 5 days, I expect to start receiving an increasing number of bug reports from users. I’m stuck in the mud here and the weekend is looming. Is there any way to escalate this?

#7

I think the only other way to reach twitter is via the Platform form

#8

Thank you, Igor!

1 Like
#9

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.