Authentication confusion

[ZeroOne3010]

The authentication part is confusing the heck out of me... The samples make it look simple, yet I cannot get it to work. My goal is to simply tweet new messages to a new Twitter bot account that I have registered.

I managed to complete the PIN-code-based authentication flow. It returned me an object like this:

Reply:  {
  accessToken: 'xxxx',
  accessSecret: 'yyyy',
  userId: 'uuuu',
  screenName: 'nnnn',
  client: TwitterApi {
    _currentUser: null,
    _currentUserV2: null,
    _requestMaker: ClientRequestMaker {
      rateLimits: {},
      clientSettings: {},
      consumerToken: 'tttt',
      consumerSecret: 'ssss',
      accessToken: 'aaaa',
      accessSecret: 'zzzz',
      _oauth: [OAuth1Helper]
    }
  }
}

Now, there alone you've got six(!) different tokens or keys... 😕 The consumerToken and consumerSecret are values that the Twitter Developer Portal also gave me when I created the app there, but there they were known as "application key" and "application secret". My code then looks like this:

const consumerClient = new TwitterApi({
  appKey: 'tttt',
  appSecret: 'ssss',
  accessToken: 'aaaa',
  accessSecret: 'zzzz'
});
console.log("Logging in to Twitter API...");
const twitterClient = await consumerClient.appLogin();
console.log("Posting to Twitter API with client ", twitterClient);
await twitterClient.v2.tweet("Hello, this is a test.");

Yet the tweet call fails to a 403 error with the detail message "Authenticating with OAuth 2.0 Application-Only is forbidden for this endpoint. Supported authentication types are [OAuth 1.0a User Context, OAuth 2.0 User Context].". What is the correct way to initialize the client?

Note that if I initialize the client like in the examples, const twitterClient = new TwitterApi('<YOUR_APP_USER_TOKEN>'); and use the bearer token given to me in the Dev Portal, it's already the consumerClient.appLogin() call that fails, this time with the error "You must setup TwitterApi instance with consumer keys to accept app-only login", which doesn't actually help me solve the issue, as I thought the other way I tried was that...

[ZeroOne3010]

Not sure what changed, but I did the whole authentication process over from the start, and now it works just like I'd expect there... 🤷