I'm using NextJS's API routes. The API cannot find the route: http://localhost:3000/api/auth/session/refresh . Do I need to add interceptors? I think the latest version of Supertokens removed the need for adding interceptors right? Using "supertokens-auth-react": "^0.27.3", "supertokens-node": "^12.1.1",

Hey

Those two are the latest versions right

please show backend debug logs

com.supertokens {t: "2022-12-05T06:41:48.722Z", message: "getSession: Started", file: "../node_modules/supertokens-node/lib/build/recipe/session/recipeImplementation.js:140:26" sdkVer: "12.1.1"} +0ms com.supertokens {t: "2022-12-05T06:41:48.722Z", message: "getSession: rid in header: true", file: "..node_modules/supertokens-node/lib/build/recipe/session/recipeImplementation.js:141:26" sdkVer: "12.1.1"} +0ms com.supertokens {t: "2022-12-05T06:41:48.722Z", message: "getSession: request method: get", file: "../node_modules/supertokens-node/lib/build/recipe/session/recipeImplementation.js:142:26" sdkVer: "12.1.1"} +0ms com.supertokens {t: "2022-12-05T06:41:48.722Z", message: "getSession: Returning try refresh token because access token from cookies is undefined", file: "../node_modules/supertokens-node/lib/build/recipe/session/recipeImplementation.js:183:34" sdkVer: "12.1.1"} +0ms

are you getting a 404 or 401 ? This is a different API that the refresh one.

As discussed, I will look into the refresh part. Any idea why email verify is receiving a 404?

I need to see all the backend debug logs when you call the api.

The above is what I got

What calls the

getSession

function? Are you calling an API that you implemented or is exposed by the middleware?

The 404 is occuring on the verify email route

have you added emailverification.init on the backend?

That was it. Thank you!