I am trying to integrate the /oauth2/register to allow users to update some of their basic details on fusion auth such as name etc.
Current system implementation involves inviting the user to fusion auth from the main application and then after that an email is sent to the user to set password. This utilises the password/change/ route
Instead of just setting up the password I want the user to be able to set up some basic information and the password. After looking at the documentation I found out /oauth2/register this would be the best possible route to implement that facility.

I tried integrating the same in the email template but ran into errors that said something was missing. redirect_uri, tenet_id, application_id were all included in query params.
Any ideas as to how exactly I should be implementing it?