Skip to main content

Testing with Postman

The following guide will go over the process of testing backend APIs with Postman. These APIs are automatically exposed via our backend SDK (/auth/* path).

important
  • Make sure that the EmailPassword Recipe is correctly setup in your backend
  • For the examples given below we will be running our backend on domain localhost and port 3001
  • The Open API spec for the APIs being tested can be found here.
  • Postman does cookie management on its own. So you don't need to manually set cookies on each request.

1. Signup#

We will first test the /auth/signup API by creating a user with an email as [email protected] and password as testPass123.

  • In Postman, set the request type to POST. Set the body of the request to be raw JSON.

  • Set the URL to http://localhost:3001/auth/signup

  • In the Header tab, set key rid with value emailpassword.

  • Add the request JSON object to the body tab as shown in the image below

  • On a successful request, a new user session will be created, with the user object and session tokens being returned in the response.

You can see the session tokens set by the response by switching to the cookies tab

These cookies are:

  • sIdRefreshToken
  • sAccessToken
  • sRefreshToken

More information about these cookies can be found here

2. Session Verification#

  • We can also test APIs which require the user to be logged in.

  • For example, we have an API used to query user data with the verifySession middleware as shown below

// The following code snippet is an example API. You do not need to // implement it in your app
app.post("/change-user-data", Session.verifySession(), async (req, res) => {    let userId = req.session.getUserId();    // mutate some user data    res.send({        user    })})
  • In Postman, set the request type to POST.
  • Set the URL to http://localhost:3001/change-user-data
  • In the Header tab, set key rid with value emailpassword.
  • If you have the antiCsrf attribute set to VIA_TOKEN in your backend SuperTokens config, then, in the Postman Header tab, set the key as anti-csrf and value as the anti-csrf token retrieved from the login response.
  • On a successful response, the response body will contain the user object
important

By default, for GET APIs, you don't need to provide the anti-csrf request header as anti-CSRF checks are only done in non-GET APIs

In case you query the /change-user-data API with an expired access token, you will get a 401 response with the message try refresh token.

To generate new session tokens you can use the /auth/session/refresh API as shown in the next section.

3. Refreshing Session Tokens#

In case your access token expires you can call the /auth/session/refresh api to generate a new access token and refresh token.

  • In Postman, set the request type to POST.
  • Set the URL to http://localhost:3001/auth/session/refresh
  • In the Header tab, set key rid with value emailpassword.
  • On a successful response, new session tokens will be set

You can see the new session tokens by switching to the cookies tab

4. Logout#

The /auth/signout API will be used to invalidate the user sessions. This will clear the session cookies set in postman.

  • In Postman, set the request type to POST.
  • Set the URL to http://localhost:3001/auth/signout
  • In the Header tab, set key rid with value emailpassword.
  • On a successful response, the session tokens will be cleared from Postman, and from the database