Custom HTTP Mailer Provider

LoginRadius allows developers to configure and integrate a Custom HTTP Mailer Provider. This functionality enables email delivery through HTTP-based APIs instead of traditional SMTP, so emails can be routed through internal notification services or modern providers such as Brevo, Resend, or Mailgun.

By supporting HTTP-based delivery, developers can align their email strategy with the same flexibility already available for SMS, the configuration process for the Custom HTTP Mailer Provider mirrors the process used to configure custom SMS/text providers and templates. You can customize authentication types, headers, body formats, and delivery endpoints to match your provider's API specifications, giving you full control over how emails are constructed and sent.

Key Features

The Custom HTTP Mailer Provider configuration offers flexibility and control, enabling seamless integration with various HTTP-based email services. Below are the key capabilities that support scalable email communication through the Admin Console.

• Integrate any third-party HTTP-based email provider, or an internal notification service, of your choice.
• Support multiple authentication methods: Basic Auth, Bearer Token, or No Authentication.
• Customize request headers, body formats, and query parameters.
• Use the same template types and placeholders already supported for SMS, for consistent, dynamic email generation.
• Fully replaces SMTP for all email-related events once configured.

Use Cases

These examples highlight practical scenarios where integrating a Custom HTTP Mailer Provider can enhance email delivery and support modern, API-driven communication requirements.

• Send transactional emails through modern HTTP-based providers like Brevo, Resend, or Mailgun.
• Route outgoing emails through an internal enterprise notification service.
• Standardize provider management by using the same HTTP-based configuration model already used for SMS.
• Leverage analytics by including custom headers or query parameters for reporting.

Configure a Custom HTTP Mailer Provider

Set up your preferred HTTP-based email service with the Admin Console by following the steps below.

1. Navigate to Admin Console > Branding > Email-SMS-Provider.

2. Select Custom HTTP Mailer Provider from the provider dropdown menu.

Configuration Fields

You'll need to fill in specific fields to complete the integration of your custom provider.

Delivery Provider URL

This API endpoint URL is used to send email requests via your provider.

• Enter the endpoint URL provided by your email provider or internal notification service.
• This URL varies by provider. Refer to the provider's documentation or use a sample cURL request to identify it.

Example cURL Request:

curl --location --request POST 'https://api.provider.com/send' \
--header 'Authorization: Bearer [Token]' \
--header 'Content-Type: application/json' \
--data-raw '{
  "to": "#receiver",
  "from_name": "#from_name",
  "from_email": "#from_email",
  "subject": "#subject",
  "text": "#body",
  "html": "#html_body"
}'

Authentication Type

Select the authentication method required by your provider's API.

• Basic Auth: Enter the username and password required by your provider.
• Bearer Token: Enter the API key or token issued by your provider.
• No Authentication: Select this option if your endpoint does not require credentials.

Body Format

Define the structure of the outgoing request body using the placeholders supported for the Custom HTTP Mailer Provider.

Format Selection

Choose the data format that matches your provider's API requirements:

• JSON: Structured data format (most common)
• x-www-form-urlencoded: URL-encoded key-value pairs

Dynamic Placeholders

The Custom HTTP Mailer Provider supports dynamic placeholders for flexible template and message construction:

Placeholder	Description
#receiver	Recipient's email address
#from_name	Sender's display name
#from_email	Sender's email address
#subject	Email subject line
#body	Plain text email body
#html_body	HTML email body

Example Payloads

• JSON Format

{
  "to": "#receiver",
  "from_name": "#from_name",
  "from_email": "#from_email",
  "subject": "#subject",
  "text": "#body",
  "html": "#html_body"
  // Add additional fields as required by your provider
}

• x-www-form-urlencoded Format

to=#receiver&from_name=#from_name&from_email=#from_email&subject=#subject&body=#body&html_body=#html_body

Note: Separate additional fields with the & character as required by your provider.

Headers (Optional)

Add any custom headers required by your provider (for example, Content-Type, Authorization, or provider-specific tracking headers).

• Enter each header as a key-value pair.
• Use headers for authentication tokens not already covered under Authentication Type, or for custom tracking/analytics metadata.

Query Parameters (Optional)

Add any query parameters required by your provider's endpoint (for example, an API key passed as a URL parameter).

• Enter each parameter as a key-value pair.
• Query parameters are appended directly to the Delivery Provider URL.

Note:

• Once a Custom HTTP Mailer Provider is configured, it entirely replaces SMTP for all email-related events; it does not run alongside SMTP as an additional channel. Events such as Forgot Password, Reset Password, Welcome Email, and Email Added, which were previously triggered via SMTP, are now sent through the configured HTTP mailer.
• The Custom HTTP Mailer Provider supports the exact same template types and placeholders currently supported for SMS: #receiver, #subject, #body, #html_body, #from_name, and #from_email.

Once all required fields are filled:

• Save your settings.
• Test the integration to confirm successful email delivery across all supported events.

Feel free to contact the LoginRadius Support team if you need assistance.

Related Resources

Email Communications and ConfigurationSMS Communication and ConfigurationCustom SMS/Text ProvidersSMTP ProvidersEmail Template Management