Invitation API with redirect_to
is it possible to add redirect_to parameter to the invitation API so that the produced confirmationURL to redirect to a specific page?
SWhat context are you using this in? and yes the
.inviteUserByEmail function does take a redirectTo option. Take a look at its docs under options https://supabase.com/docs/reference/javascript/auth-admin-inviteuserbyemailSupabase API reference for JavaScript: Send an email invite link
Mwell I'm using the invitation and the registration APIs through an automation in make.com and I'm sending (for registration) on (https://.../auth/v1/signup):
and for invitation on (https://.../auth/v1/invite)
but it doesn't seem to respect it, it just redirects to the Site URL which is just the root url of the domain
and for invitation on (https://.../auth/v1/invite)
but it doesn't seem to respect it, it just redirects to the Site URL which is just the root url of the domain
Mthe problem is on the redirect_to= url parameter of the confirmationURL as it is resolving when clicked from the email
SYou will need to check out what the REST API expects because the JS client takes those as an options object and not direct property.
Mwhere can I find this? I tried the API page of the project that also gives the cURL syntax but it doesn't show all properties that are available
SBest bet is the GitHub page for Supabase Auth or you can just fire up the JS SDK and make a request to see what is being sent.
Mbut it is on the same domain, I thought white-listing was needed for external domains
SNo it's necessary for same domain too.
Myou mean here right?
or somewhere else?
or somewhere else?
Mah ok
MI'll try it out, thanks!
SIf your website is in production please don't leave any reference to
localhost in your production projects. This is a security issue as someone can easily spoof localhost from their own domain and do phishing with your brand.SThis is what branching is for or prior to branching you should have separate projects for each environment.
SFor dev I just use local Supabase CLI. Then for staging just use one of your free projects you are allowed per account.
SUse database migrations to keep schemas in sync and never make changes to tables or schemas from the dashboard (staging and production).
Mwell it works!! thank you both!
SJust to be clear this isn't Supabase specific advice, it's been industry practice for years now. Just that indie hackers don't see to know these practices and make changes in production as and when they feel like.
