Replies: 2 comments 2 replies
-
Sorry for the trouble. I resolved it by URL decoding the key part. |
Beta Was this translation helpful? Give feedback.
1 reply
-
FWIW, you are free to use |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a question regarding email address verification with a headless API.
During sign-up and when logging in, if the email address verification has not yet been completed, the following setting:
HEADLESS_FRONTEND_URLS = {
"account_confirm_email": "http://localhost:5173/verifyemail/{key}",
}
generates a link like the one below:
http://localhost:5173/verifyemail/OQ%3A1s9z3J%3AfCY4YEaJ2b0SLqLl00brSdlLbUXG73E5Cmgkdi9F16k
Is the key the part after "verifyemail/", which is "OQ%3A1s9z3J%3AfCY4YEaJ2b0SLqLl00brSdlLbUXG73E5Cmgkdi9F16k"?
Also, the client requires the X-Session-Token when using the app. Should we use the session_token obtained during sign-up or login?
Beta Was this translation helpful? Give feedback.
All reactions