API returned unauthorized #30
Comments
it's not giving me a new token. Still the same after reseting the config file. I still have the same error message. |
My bad I just double checked with fansly api, it seems like they've removed the authentication token from the apiv2 requests. They're mainly using api version 3 now and the authentication token is only inside the api version 3 requests (which automatic configurator is not finding). You've to type in I will fix all this within the next couple days. I expected this to happen, you can read about it here: #23 |
Yeah I read that too. So I tried with "apiv3" but I cant find anything with this search. Am I doing it wrong or it's normal till you fix it ? |
But I am not sure to understand step 3.. I dont see how I have to "locate a request" |
When you type in "apiv3" where it asks you to in step 2 (on the picture), there'll only be a couple entries in the "names" field. One of them will be But if you don't understand how to do this, you'll have to wait for me to publish the next update. Which I'll be doing once the repository reaches 200 stars. |
It's ok, I find out ! it's because it wasnt looking the same to me than in the screenshot. It's working now ! thank you very much ! |
fixed a bug: + where api would return unauthorized (#30) + where login request no longer returned auth token (#18) changes: + added support for two factor authentication with automatic configurator module changes: + removed requirement for module selenium_wire entirely + adjusted automatic configurator for undetected_chromedriver > 3.1.5 (please update using "pip install --upgrade undetected_chromedriver")
Fixed in version v0.3.4 |
Hey,
firstly thank you for this, it's really a nice tool to use !
I used it several times without issues. I didnt change anything but now I have this message : [11]ERROR | 20:56 || API returned unauthorized. This is most likely because of a wrong authorization token, in the configuration file.
But I cant change the authorization token.
Can you tell me what to do there ? Thank you very much !
The text was updated successfully, but these errors were encountered: