When I try to use the use functions in the frontend (Angular)

ts
// login function
  async login(email: string, password: string) {
    console.log(
      await ThirdPartyEmailPassword.emailPasswordSignUp({
        formFields: [
          {
            id: 'email',
            value: email,
          },
          {
            id: 'password',
            value: password,
          },
        ],
      })
    );
  }

I get 404 error, stating that the route in the backend (NestJS) does not exist

POST http://localhost:3333/api/signup 404 (Not Found)

. What am I supposed to do, in order for the backend to to the correct think on those routes?

My stack: Next.js frontend Nest.js backend Postgres 1. Getting Next.js to work with SuperTokens seems easy. However, once the user has logged into the Next.js app and starts making API calls, how does the Nest.js app know if the user has logged in from the API calls? 2. I'd like to store user details such as email, auth provider, etc. on my own Postgres database. Is there some kind of callback that will send a request to my API when the user changes email or a new account has just been created?

hey :). we are having an issue with the redirect uri returned for Apple on the web. the code that creates the redirect uri uses the API base path instead of the UI base path.

I discovered today that Playwright might give devs access to the browser's cookies. (Would have to confirm on my own.) If they do, it could be a great tool for testing example repositories since it also enables devs to disable JavaScript in the browser during end to end testing. If a set of standard test cases could be created, they could be run against any example repo to make sure everything still works as expected during repo NPM package upgrades, etc. Hoping to look into this sometime within the next 4 months. But sounds pretty exciting (since it would take away a lot of manual work).

Hello, I have a question about my use-case that I'm exploring. For the app that I am working on, I have three components: - Web Frontend Application (React+Vite) - Backend Application (NestJs) - Mobile Application (React Native) And I have to support two types of authentication: Email+Password, Passwordless (Using SMS, for mobile application). I am more interested to self-host it, but my other partner wants to use the cloud version. I have some questions for cloud version: - How does the pricing work? if I have 5001 MAU, would my bill be $100 or $0.02? - Since we have the use-case of sending SMS, is it handled by Supertokens in the pricing? - How easy is it move from self-hosted to cloud and vice-versa? - How good is the support if we end up using the cloud version? - When we sign up user with email password, we take multiple inputs apart from email, password, first name, last name. Additional inputs would be company name, tax id, city, phone number. Is it possible to extend the signup form with additional inputs? Thank you to whoever takes their time to answer this. Really appreciate it.

Heyo there ! 👋 Are those features available for free while self hosting SuperTokens ? - SSO - B2B / API Keys distribution for server to resource server communication / Micro service auth - Authorization through RBAC / Role management - A2F Thanks a lot to anyone who will take time to answer this ! 🙏

hi, i faced an issue.

Error: SuperTokens core threw an error for a POST request to path: '/recipe/accountlinking/user/primary' with status code: 402 and message: Account linking feature is not enabled for this app. Please contact support to enable it.

Hey, I have a problem wih usiing the passwordless recipe. I am using the python SDK with fastapi in my backend, custom ui (supertokens-web-js) on the frontend and a selfhosted core. All are updated to the latest version. (0.18.7 / 0.9.1 / 7.0). Here be backend config for the passwordless recipe:

python
passwordless.init(passwordless.ContactConfig(
        contact_method='EMAIL'),
        flow_type='USER_INPUT_CODE_AND_MAGIC_LINK',
    )

And this is the rontend config:

ts
import SuperTokens from 'supertokens-web-js';
import Session from 'supertokens-web-js/recipe/session';
import Passwordless from 'supertokens-web-js/recipe/passwordless'

const initSupertokens = () => {
    SuperTokens.init({
        appInfo: {
            apiDomain: process.env.NEXT_PUBLIC_BACKEND_HOST!,
            apiBasePath: "/auth",
            appName: "CM",
        },
        recipeList: [
            Session.init(),
            Passwordless.init({}),
        ],
    });
}

export default initSupertokens

after calling

import { createCode } from "supertokens-web-js/recipe/passwordless";
...
const resp = await createCode({email})

i am getting

res.status = OK

Also my backend loggs:

"POST /auth/signinup/code HTTP/1.1" 200 OK

and returns:

json
{
    "status": "OK",
    "deviceId": "cY1ju3u88Tl7IDYc/JBf3duXTHoTbeAz5ujFr0ThODI=",
    "preAuthSessionId": "2S0TLFvqwGH9jX7KRM-IBnS4oP8nd8e-JkmsB0JnilY",
    "flowType": "USER_INPUT_CODE_AND_MAGIC_LINK"
}

But i am not getting any email. I tested several email addresses.

Hi, I would like to use nock to mock the API call behaind

thirdPartySignInUpPOST

because of some account linking logic we do after it that I would like to test. can you help me understand how the request path looks like and what should be an example of the response? I'm going to use nock to do that if it makes any difference for you

Is there any documentation on best practices when self-hosting SuperTokens Core? I was thinking if it is feasible to run the core on a Cloud Run service instance. Thoughts?