So you should keep the

.middleware()

, but you can specifically disable the sign in / up API routes by setting

disableDefaultImplementation

to

true

in the

signUpFeature

and

signInFeature

objects when calling the

init

function: See https://supertokens.io/docs/nodejs/thirdpartyemailpassword/init Then, you can create your own API route: - {authBasePath}/signinup POST (for sign in / up via social login): https://github.com/supertokens/frontend-driver-interface/blob/master/v1.7.0.md#url-apibasepathsigninup - {apiBasePath}/signin POST (for sign in via email password): https://github.com/supertokens/frontend-driver-interface/blob/master/v1.7.0.md#signin-api - {apiBasePath}/signup POST (for sign up via emailpassord): https://github.com/supertokens/frontend-driver-interface/blob/master/v1.7.0.md#url-apibasepathsignup When you create your own routes, make sure the path and method match the above API spec so that the frontend continues to work. Our implementation of these APIs can be found: - {authBasePath}/signinup POST: https://github.com/supertokens/supertokens-node/blob/master/lib/ts/recipe/thirdparty/api/signinup.ts - {apiBasePath}/signin POST: https://github.com/supertokens/supertokens-node/blob/master/lib/ts/recipe/emailpassword/api/signin.ts - {apiBasePath}/signup POST: https://github.com/supertokens/supertokens-node/blob/master/lib/ts/recipe/emailpassword/api/signup.ts