Getting "403 Forbidden" responses from the Twitter API?

Today I spent some time not understanding why my request to Twitter was failing. It replied with 403 Forbidden, but I was pretty confident the accessToken was correct. What could it be? I double, tripled checked my code.

Then I turned to my frenemy Google and found the answer way down there in an old forum thread. I had probably not requested the correct scope when authenticating the user.

As always, the information is right there in plain sight in the documentation 🤦‍♀️

Tweet with image of the documentation

However, I set up the NextAuth with Gatsby integration weeks ago, and their default scope settings have worked perfectly so far 😱

To override NextAuth's default scope authorization.params.scope to your TwitterProvider configurations.

export const authConfig = {
  // Configure one or more authentication providers
  providers: [
      clientId: process.env.TWITTER_CLIENT_ID,
      clientSecret: process.env.TWITTER_CLIENT_SECRET,
      version: "2.0",
      // 👇👇👇
      authorization: {
        params: {
          scope: "",

I hope you remember this when you need it or find it again when you need it. I'll probably google and land back on this myself the next time this happens to me 🤪


All the best,
Queen Raae

Interested in more daily treasures like this one?
Sent directly to your inbox?