A Blueprint can be directly invoked or a Trigger can be used to create a Business Process within a Blueprint. https Triggers are publicly accessible so use them appropriately.

To do so, you would use https://api.authvia.com/v3/Triggers/{Trigger-id} where Trigger-id is your Trigger's id. You can then use a GET or POST Action against the path based on your integrations need.

GET

When using a https:GET Trigger the querystring provided is converted to the payload. The https:GET Trigger supports redirect functionality through the redirect_uri querystring parameter, which will cause the user to be redirected after the Trigger is invoked.

Customer Signup Flow

If the {ref} parameter is not defined in the trigger URL and the merchant has customer signup configured, the system will automatically:

Redirect the user to the customer signup form to create their account
After successful signup, redirect back to the original trigger URL
Execute the trigger with the newly created customer reference
Apply the redirect_uri parameter (if provided) to redirect the user to the final destination

This flow ensures that customers can seamlessly sign up and then proceed with the intended business process without manual intervention.

Example Usage

https://api.authvia.com/v3/Triggers/{trigger-id}?redirect_uri=https://your-app.com/dashboard

If no {ref} is provided and customer signup is configured, users will be guided through the signup process before the trigger executes and redirects to the specified redirect_uri.