Existing User Invitation: Self-Hosted UI

If you intend to self-host the Existing User Invitation Page and utilize Wristband APIs to facilitate the Existing User Invitation Workflow, it is necessary to override the Action Link URL for the Existing User Invitation Email Policy in the Wristband Dashboard for your application. The URL value should point to the location of your application's self-hosted Existing User Invitation Page.

At a high level:

1. The user clicks on the Action Link in the Existing User Invitation Email that was sent to their inbox.
2. The user is redirected to your application's self-hosted Existing User Invitation Page.
3. The user submits the form.
4. Your application calls the Wristband Accept Existing User Invite API, passing along the Email Authorization Code.
5. Your application then redirects the user to the Wristband Create Auth Session for Existing User Invite API in order to create a Wristband Authentication Session for the user. The redirect URL is returned in the response from the prior step as well as an Auth Session Code that is required to successfully create the session.
6. Wristband redirects the user to the Login Endpoint implemented by your application.

From here, the user would be sent through the Authorization Code Flow in order to log in and gain entry to the application. Because Wristband already created an Authentication Session for the user during the flow, the user gains immediate entry into the application without having to re-enter their credentials.