token value is null when using getToken

[deadcoder0904]

I'm still following https://spacejelly.dev/posts/how-to-make-twitter-api-requests-with-nextauth-js-session-tokens/ & I have /api/twitter/search endpoint that looks like:

import { NextApiRequest, NextApiResponse } from 'next'
import { getSession } from 'next-auth/react'
import { getToken } from 'next-auth/jwt'

export default async (req: NextApiRequest, res: NextApiResponse) => {
  try {
    const session = await getSession({ req })
    const token = await getToken({
      req,
      token: process.env.NEXTAUTH_SECRET,
    })

    console.log({ session })
    console.log({ token })
    return res.status(200).json({
      status: 'Ok',
      data: [],
    })
  } catch (e: unknown) {
    return res.status(400).json({
      status: (e as Error).message,
    })
  }
}

I get the token value to be null but I do have session value. How do I get the token value? The blog post used v3 so not sure if something changed in v4.

Full repro is on branch next-auth-with-twitter-api-v2 → https://github.com/deadcoder0904/twitter-api-v2-3-legged-login-using-next-connect/tree/next-auth-with-twitter-api-v2

[balazsorban44]

You have a typo:

getToken({
  req,
  secret: process.env.NEXTAUTH_SECRET
})

tip, you probably don't need both getSession and getToken. session is the subset of token in most cases, depending on what you do in your session callback

[balazsorban44]

Yes. As said, Twitter is an OAuth 1 provider, and so it returns those tokens with different names. Please read above.

Here is a link to Twitter terminology https://developer.twitter.com/en/docs/authentication/oauth-1-0a/obtaining-user-access-tokens

[deadcoder0904]

yes i saw that & found this:

but not sure where do i get refresh_token? also, access_token is oauth_token?

[deadcoder0904]

besides since this library is typed, i don't get oauth_token as a method when i do account.

i only get account.access_token & account.refresh_token when i do autocompletion.

[balazsorban44]

I'm actually not familiar with the OAuth 1 flow other than that difference. I haven't used the Twitter API in the past. You might have to do your own research how to use the returned tokens.

[balazsorban44]

For type augmentation, refer to https://next-auth.js.org/getting-started/typescript