OAuth tool not able to do a POST for request_token, why?

RBT3CH · 2013-08-19T19:36:49.000Z

Hi guys,

I’m getting 401’s when I try to do a POST to https://api.twitter.com/oauth/request_token using my own PHP code, I know that there may be a problem somewhere along the lines of my signature, etc. but I’ve checked my signature_base_string and oauth_signature with other working PHP libraries, so have narrowed it down to possibly how I send the request, anyways, so I wanted to compare with the OAuth tool’s OAuth signature, etc. but when I try the generated cURL command, I also get a 401?!

At first I thought it was the “read-write” permissions, https://dev.twitter.com/docs/faq#20277 but even after making the change, I still got the same error.

Please let me know what I’m missing or need to do, I am trying to implement sign in with Twitter (https://dev.twitter.com/docs/auth/implementing-sign-twitter).

episod · 2013-08-20T15:08:23.000Z

The OAuth tool is best suited for preparing requests to the API resource methods more so than the OAuth step-by-step flow.

Can you provide an example of what your POST to oauth/request_token looks like without exposing your token secrets? I assume your system clock is accurate?