My bot has stopped working, how to handle new x-twitter-auth-type/authorization

Hi All,

I have a free twitter bot people use. A month or so ago it stopped being able to follow/unfollow due to changes in the way twitter works. Look like they've change the URL (which is obviously easy to change in my code) and the auth for following/unfollowing. Anyone know how to generate the new authorization bearer header? I can't see the token anywhere in the HTML or headers the twitter server outputs. There is a reference in the webpack JS https://ma-0.twimg.com/twitter-assets/responsive-web/web/ltr/main.567ae3b46963f1df.js about BEARER_TOKEN are you guys just parsing that?

Any advise from fellow botters welcome

I found this Bearer in this file:
https://abs.twimg.com/k/en/init.en.37d4e85afd8ede9741dd.js
Bearer = 'Bearer AAAAAAAAAAAAAAAAAAAAAPYXBAAAAAAACLXUNDekMxqa8h%2F40K4moUkGsoc%3DTYfbDKbT3jJPCEVnMYqilB28NHfOPqkca3qaAxGfsyKCs0wRbw'

next2doors said:

I found this Bearer in this file:
https://abs.twimg.com/k/en/init.en.37d4e85afd8ede9741dd.js
Bearer = 'Bearer AAAAAAAAAAAAAAAAAAAAAPYXBAAAAAAACLXUNDekMxqa8h%2F40K4moUkGsoc%3DTYfbDKbT3jJPCEVnMYqilB28NHfOPqkca3qaAxGfsyKCs0wRbw'

Click to expand...

Thanks man, I'll take a look

I can look over the code for you for free. PM if interested.

Charles Roberto said:

I can look over the code for you for free. PM if interested.

Click to expand...

Thanks for the offer mate, but I got this sorted now. Extracted the bearer from is and cto csrf token header is in the cookie. So it's all good