Set up email provider
Many authentication use cases require sending emails to your users. Whether they are looking to verify their email address, reset their password, or be alerted of password changes, your users will need to receive these emails. This page shows the options for configuring email providers via the ReachFive Console.
See the Email templates page if you are looking for templates. |
ReachFive integrates with the following email SaaS services:
We also provide:
|
SMTP providers
You should use the SMTP provider to send emails if you have a reliable SMTP server available that will be able to handle all automated email distribution.
SMTP provider setup
-
In the ReachFive Console, go to
. -
Enter the SMTP configuration details.
-
Specify the
From
email address. This is what the recipients see as who sent the email. -
Enter any
Reply to
email addresses that you wish to have. (Optional)When users reply, it will be sent to these emails. -
Enter the host for your SMTP server.
-
Enter the port for that host SMTP server.
-
Enter your username for the SMTP server.
-
Enter the password associated with the above username for the SMTP server.
-
Check
SSL
orTLS
depending on your requirements.
-
-
Select Send test email to validate the configuration.
The email is sent to the address of the user currently logged in. -
Don’t forget to Save your input.
Custom providers
You should use the generic Email API to send emails when:
-
ReachFive Console does not provide a native integration with your SaaS solution. You need to implement the generic email API, and then send your emails from your system as you would.
-
You use a custom or in-house piece of software to manage emails. You will need to implement our generic API and then map the data sent to your template and email service.
Provider setup
-
In the ReachFive Console, go to
. -
Select Custom provider
-
Select the endpoint where you would like ReachFive Console to send email requests.
When sent, the REQUEST and payload
are set and not customisable. -
If needed, enter the
HTTP Authorization value
. For example:Basic dm9yZGVsOnZvcmRlbA==
. (Optional) -
Select Send test email to validate the configuration.
The email is sent to the address of the user currently logged in. -
Don’t forget to Save your input.
- Select the endpoint where you would like ReachFive to send email requests
-
An example request and payload are as follows:
POST https://YOUR_DOMAIN
{ "email": "clarence@example.com", "template_id": "verify_email", (1) "personalizations": { "id": "id", "external_id": "externalId", "given_name": "Max", "last_name": "Robertson", "gender": "M", "has_password": "true", (2) "lang": "fr", "verification_code": "verificationCode", "redirect_url": "https://www.example.com/redirect" } }
1 The template_id
is the email template. This is the ID for the template found at or alternatively for MFA at .2 The has_password
boolean is only included in the payload for thepassword_reset
template.
The
|