Hi, we have implemented thirdpartyemailpassword recipe along with emailverification recipe. But for some users, they didnt verified their emails with the login provider. So their emails not marked as verified. For those users, when we try to call an api, we are getting claims not verified error. How to get access the api without needing to verify their emails?

Hi could I get some assistance? I am working on a feature where I want to send a link as part of a confirmation email. I would like to create a magic link that authenticates a user and allows them to cancel a booking. I have been looking at this documentation https://supertokens.com/docs/thirdpartypasswordless/custom-ui/login-magic-link but I don’t necessarily want the email to be sent automatically as we have a trigger through Salesforce Marketing Cloud and I would to pass in a token as part of this magic link. But I am not sure how to proceed. Any advice would be appreciated.

How soon is "soon" ? and it seems like there's still a partial support for mongodb, to what extent can I use it? Can I fully rely on it?

Hello, I cannot access the ST dashboard on my backend anymore (core):

/email/exists endpoint fails for social media accounts. it seems that it only works for email account. any ideas how to impprove (override) it to support social accounts as well?

Getting invalid api when curling to create a dashboard user with supertokens server -> curl --location --request POST 'Server link' \ --header 'rid: dashboard' \ --header 'api-key: ' \ --header 'Content-Type: application/json' \ --data-raw '{"email": "","password": ""}'

Hello! Wondering if there's any method I could do this manually? Plan to send it via SendGrid and handle it with my own form on the frontend.

I have my website deployed and I am getting the following error when trying to sign in using an account I created on localhost (connected to the same supertokens hosted instance) Error: No SuperTokens core available to query at Querier. (/home/rscsguex/nodevenv/api-development/14/lib/node_modules/supertokens-node/lib/build/querier.js:225:27) at Generator.next () at /home/rscsguex/nodevenv/api-development/14/lib/node_modules/supertokens-node/lib/build/querier.js:30:75 at new Promise () at __awaiter (/home/rscsguex/nodevenv/api-development/14/lib/node_modules/supertokens-node/lib/build/querier.js:12:16) at Querier.sendRequestHelper (/home/rscsguex/nodevenv/api-development/14/lib/node_modules/supertokens-node/lib/build/querier.js:218:13) at Querier. (/home/rscsguex/nodevenv/api-development/14/lib/node_modules/supertokens-node/lib/build/querier.js:245:43) at Generator.throw () at rejected (/home/rscsguex/nodevenv/api-development/14/lib/node_modules/supertokens-node/lib/build/querier.js:22:44) at processTicksAndRejections (internal/process/task_queues.js:95:5)

thirdPartySignInAndUp

gives me the following error. CORS configuration should be good as it works fine for normal sign in/up with credentials. Any ideas?

I am getting this 500 internal server error - custom ui, nestjs backend