Skip to main content

NestJS Integration Guide

Integrating SuperTokens into a NestJS backend is a bit different than the quick setup guide shows. We will add a few things:

  • A module to house all authorization-related code
  • A service to initialize the SDK
  • A middleware to add the authorization endpoints
  • A global error handler to pass SuperTokens related errors to the SDK
  • A guard to protect your API endpoints
  • A parameter decorator to access the session in your code

We will cover each of these in the following few sections. Then, you can do the rest of the customizations by following the "Auth Flow Customizations" section.

Please look here to see how to get started with your NestJS backend.

Installing SuperTokens#

npm i -s supertokens-node

Adding a new module#

You can scaffold a module using the nest CLI by running this in the root folder of the application:

nest g module auth

The result should be a new auth folder with auth.module.ts in it.

Add config type and injection token#

Create a config.interface.ts in the auth folder. We will put the type and injection token for the SuperTokens configuration here.

import { AppInfo } from 'supertokens-node/types';

export const ConfigInjectionToken = 'ConfigInjectionToken';

export type AuthModuleConfig = {
appInfo: AppInfo;
connectionURI: string;
apiKey?: string;

Configure the Auth module#

In auth.module.ts, add the following authorization-related code:

import { Module } from '@nestjs/common';
import { SupertokensService } from './supertokens/supertokens.service';
import { MiddlewareConsumer, NestModule, DynamicModule } from '@nestjs/common';
import { AuthMiddleware } from './auth.middleware';
import { ConfigInjectionToken, AuthModuleConfig } from './config.interface';

providers: [],
exports: [],
controllers: [],
export class AuthModule implements NestModule {
configure(consumer: MiddlewareConsumer) {

static forRoot({
}: AuthModuleConfig): DynamicModule {
return {
providers: [
useValue: {
provide: ConfigInjectionToken,
exports: [],
imports: [],
module: AuthModule,

In the provided code sample, we convert this to a dynamic module so we can configure parts of the SuperTokens setup within the App module. This approach allows for centralized configuration, which can be particularly beneficial when managing settings such as using distinct connection URIs for different environments, such as testing or production.


The middleware is registered using the configure method in the AuthModule class.

Adding the module to the application#

Update the app module to use the dynamic module returned by the forRoot method of the AuthModule instead of directly importing the class itself.

// ...
import { Module } from '@nestjs/common';
import { AuthModule } from './auth/auth.module';

imports: [
connectionURI: "",
apiKey: "",
appInfo: {
// Learn more about this on
appName: "<YOUR_APP_NAME>",
apiDomain: "<YOUR_API_DOMAIN>",
websiteDomain: "<YOUR_WEBSITE_DOMAIN>",
apiBasePath: "/auth",
websiteBasePath: "/auth"
controllers: [/* ... */],
providers: [/* ... */],
export class AppModule {}

Adding a service#

Run the following Nest CLI command from the root to scaffold a service:

nest g service supertokens auth

In the newly created supertokens.service.ts file, initialize the SDK so that you can access the injected services in event handlers:

import { Inject, Injectable } from '@nestjs/common';
import supertokens from "supertokens-node";
import Session from 'supertokens-node/recipe/session';
import EmailPassword from 'supertokens-node/recipe/emailpassword';

import { ConfigInjectionToken, AuthModuleConfig } from "../config.interface";

export class SupertokensService {
constructor(@Inject(ConfigInjectionToken) private config: AuthModuleConfig) {
appInfo: config.appInfo,
supertokens: {
connectionURI: config.connectionURI,
apiKey: config.apiKey,
recipeList: [

Exposing SuperTokens APIs using its middleware#

The middleware file#

Scaffold the middleware by running nest g middleware auth in the application's root folder. The result should be in the auth module, called auth.middleware.ts.

Next, edit the file to use the middleware from SuperTokens:

import { Injectable, NestMiddleware } from '@nestjs/common';
import { middleware } from 'supertokens-node/framework/express';

export class AuthMiddleware implements NestMiddleware {
supertokensMiddleware: any;

constructor() {
this.supertokensMiddleware = middleware();

use(req: Request, res: any, next: () => void) {
return this.supertokensMiddleware(req, res, next);

Update CORS settings#

Enable and update your CORS settings in main.ts:

import { NestFactory } from '@nestjs/core';
import supertokens from 'supertokens-node';
import { AppModule } from './app.module';

async function bootstrap() {
const app = await NestFactory.create(AppModule);
origin: ['<YOUR_WEBSITE_DOMAIN>'],
allowedHeaders: ['content-type', ...supertokens.getAllCORSHeaders()],
credentials: true,

await app.listen(3000);


Add the SuperTokens error handler#

We will add the SuperTokens error handler through a NestJS exception filter.

Exception filter#

You can scaffold the exception filter using the CLI by running: nest g filter auth. This will result in a new auth.filter.ts file next to auth.module.ts. Edit this file to add the error handler:

import { ExceptionFilter, Catch, ArgumentsHost } from '@nestjs/common';
import { Request, Response, NextFunction, ErrorRequestHandler } from 'express';

import { errorHandler } from 'supertokens-node/framework/express';
import { Error as STError } from 'supertokens-node';

export class SupertokensExceptionFilter implements ExceptionFilter {
handler: ErrorRequestHandler;

constructor() {
this.handler = errorHandler();

catch(exception: Error, host: ArgumentsHost) {
const ctx = host.switchToHttp();

const resp = ctx.getResponse<Response>();
if (resp.headersSent) {


Registering the filter#

We need to add this filter as a global exception filter. You can do this in main.ts, right after the updated CORS settings.

import { NestFactory } from '@nestjs/core';
import { AuthModule } from './app.module';

import supertokens from 'supertokens-node';
import { SupertokensExceptionFilter } from './auth/auth.filter';

async function bootstrap() {
const app = await NestFactory.create(AuthModule);
origin: ['http://localhost:3001'], // TODO: URL of the website domain
allowedHeaders: ['content-type', ...supertokens.getAllCORSHeaders()],
credentials: true,

app.useGlobalFilters(new SupertokensExceptionFilter());

await app.listen(3000);


Add a session verification guard#

Now that the library is set up, you can add a guard to protect your API. You can scaffold this by running: nest g guard auth.

In the newly created auth.guard.ts file, implement session verification:

import { CanActivate, ExecutionContext, Injectable } from '@nestjs/common';
import { Error as STError } from "supertokens-node";

import { verifySession } from 'supertokens-node/recipe/session/framework/express';
import { VerifySessionOptions } from 'supertokens-node/recipe/session';

export class AuthGuard implements CanActivate {
constructor(private readonly verifyOptions?: VerifySessionOptions) {}

async canActivate(context: ExecutionContext): Promise<boolean> {
const ctx = context.switchToHttp();

let err = undefined;
const resp = ctx.getResponse();
// You can create an optional version of this by passing {sessionRequired: false} to verifySession
await verifySession(this.verifyOptions)(
(res: any) => {
err = res;

if (resp.headersSent) {
throw new STError({
message: "RESPONSE_SENT",

if (err) {
throw err;

return true;

Add a parameter decorator#

Now you can add a parameter decorator to access the already verified session in your APIs. You can generate an empty decorator by running nest g decorator session auth. Edit session.decorator.ts to return the session attached to the request:

import { createParamDecorator, ExecutionContext } from '@nestjs/common';

export const Session = createParamDecorator(
(data: unknown, ctx: ExecutionContext) => {
const request = ctx.switchToHttp().getRequest();
return request.session;

Combine the decorator and the guard to authenticate users#

You can add a protected method into a controller (e.g., app.controller.ts) that receives the verified session as a parameter. For example:

import { Controller, Get, UseGuards } from '@nestjs/common';
// ...
import { SessionContainer } from "supertokens-node/recipe/session";
import { AuthGuard } from './auth/auth.guard';
import { Session } from './auth/session/session.decorator';
// ...

export class AppController {
// ...
@UseGuards(new AuthGuard())
async getTest(@Session() session: SessionContainer): Promise<string> {
// TODO: magic
return "magic";

You should look at the "Session Management" section to see how you can use the session object.

Setup the SuperTokens core#

Are you using as the connection URI in the init function?