-
-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API not working anymore? [Unauthenticated calls work now, but not auth] #7
Comments
hey could you please provide the full error? thanks :)
|
Sorry for the late reply, I was able to debug a bit more and have come to this minimal code:
Which prints:
I was also able to manually obtain the access token (by looking in the browser), and when I try to run usual commands, I get:
Is it possible they modified their API? Does the current library still work for you or others? Thanks, I hope I can figure it out, it's been super useful. |
They modified their API to require some additional headers as well as adding an extra slash after the URL... but i fixed it in latest commit :) #f6ef128 Still haven't fixed the login yet but i'm working on it rn :) |
Hey @wxllow , I appreciate your help. I appreciate that you might not have time to work on this, so no worries. I'd be happy to help, but I am unsure on a how to "reverse engineer" their API and its requirements... |
What I do to reverse engineer their API is basically going on the website and using the Network tab in Chrome's developer tools to analyze the requests that the site makes to their APIs |
Haven't changed anything, but recently not able to log in anymore.
When posting to
https://api.whatnot.com/api/login
I am now getting[400 Bad Request]
, even though I've verified the email/pwd multiple times.Anybody else seeing this?
The text was updated successfully, but these errors were encountered: