https://supertokens.com/ logo
Join Discord
Powered by
want to ask why sign up API is not exposed with em...
# support-questions-legacy
r
want to ask why sign up API is not exposed with emailpassword recipe?
r
hey @Raian
it is exposed.
which spec are you seeing>?
that doesb't seem like ours
r
swagger
even postman cant reach it
r
can you send me a link?
to the swagger spec that u r seeing
r
its local
r
this is the swagger spec supertokens exposes
im not sure what swagger you are referring to to be honest
please see the link i sent above
r
also cant find signup
r
r
is it supposed to be signin instead of sign-in?
r
it's pretty clear in the spec above.
r
hm ok i had been staring at the wrong API section sry about that now the APIs are not exposed at all
r
Have you followed our guides?
r
yeah
r
And used our backend SDK middleware?
r
r
Right.
So please enable backend debug logs
And show me the output when you call one of the APIs
What’s the apiBasePath you have added to your backend config? (In appInfo object)
By default the value of the is /auth
r
/auth
r
So if you haven’t added that config, then try querying /auth/signin
Instead of /api/auth/signin
r
oh
r
Or else change the apiBasePath in the backend to /api/auth
r
ohhh ok
how to make it show up in swagger though?
swagger is currently under localhost:3000/api
r
Ah right. That you can’t.
Cause the APIs are exposed implicitly
If you want to have them on swagger, you will have to make those APIs yourself and use the functions provided by our backend SDK
But not worth the effort tbh. Just use our middleware
r
hmm ok thanks
lets say if i were to have them exposed on swagger, are there any references for the API implementations?
r
Our SDK is open source. You can see the code 🙂
PreviousNext
Powered by