Goodreads Developers discussion

54 views
questions > Full OAuth request_token URL

Comments Showing 1-6 of 6 (6 new)    post a comment »
dateUp arrow    newest »

message 1: by Fred (new)

Fred | 5 comments I'm using vanilla JS to authenticate with OAuth. The URL I'm using returns a 401, either in my app or testing with Postman.

The format I'm using is: https://www.goodreads.com/oauth/reque.... I've also tried adding '&head=True' or '&header=True'.

What am I missing here? Thanks in advance!


message 2: by Michael (new)

Michael Ross | 3 comments I'm having similar issues - I'm able to get oauth_token and oauth_token_secret using the format you have above in postman, but any subsequent API calls fail.


message 3: by Fred (new)

Fred | 5 comments @Michael, that's so annoying. Did you use head or header? And did you do a GET or POST request? I can't get either to work.


message 4: by Michael (new)

Michael Ross | 3 comments I tried both body and headers; I only tried GET originally (since I'm not creating or mutating an entity), but I just tried POST and got 404 (not found) instead of 401 (not authorized), so I think GET is the way to go.


message 5: by Michael (new)

Michael Ross | 3 comments I also tried walking through all the signature methods (SHA1, 256, plaintext) to no avail.

To be fair, I'm more of a data engineering nerd than a front-end dev, so navigating OAUTH, and using Postman, isn't second nature to me. I'll try getting it working in python over the weekend.


message 6: by Fred (new)

Fred | 5 comments Not my bag either, thanks for the help. I got the GET working (at least once).


back to top