Getting User Info & Limit about tmhoauth

[themattharris]

Hey cypherD,

For question 1, make sure the token and secret are valid for the user you are making requests on behalf. For testing you can find out your own on dev.twitter.com/apps - and yeah the 150 limit means it considers you unauthenticated.

For question 2, the correct endpoint is https://api.twitter.com/1/account/verify_credentials.json (without the username) (doc: https://dev.twitter.com/docs/api/1/get/account/verify_credentials).

As you are getting the error "Could not authenticate with OAuth" and also "expired token" i'm pretty certain the issue is either incorrect or temporary tokens are being passed in your requests. The best thing to do here is copy your own token/secret from dev.twitter.com/apps and see if that works. If it does, you know something is wrong in the way you obtain or store the user tokens in the the live app.

Some of the API endpoints on the Twitter API will default to unauthenticated if the credentials you are sending are invalid. If this happens there will be a header X-Warning added to the response which you can inspect by doing var_dump($tmhOAuth->response['headers']);. If the credentials were bad the header will read:

x_warning: Invalid OAuth credentials detected

I think this is why the token is allowing you to access the 10 favorite tweets (unauthenticated) but doesn't allow you to access protected 'authenticated only' resources.

Let me know how you get along with the token/secret from dev.twitter.com/apps

[Scottjutsu]

Spot on. It seems I tripped up somewhere among all of the steps of the 'OAuth dance', as you aptly put it. Thanks so much!

[themattharris]

Great, glad you got it working!