As per documentation of the WCQS endpoint, there is no current way other than in the browser to generate the token required to actually authenticate to WCQS. While we are tracking the community request to disable authentication (T297995), as long as that seems unlikely to be actioned, one of the ways to mitigate the effects of that issue would be to improve the authentication experience. Not being able to authenticate by bot (or, importantly, reauthenticate without human intervention when a session expires while a bot is running), is a major drawback of the current system, which could be fixed to lessen the difficulties that authentication has introduced.