Knowledge Base Connect a provider Connecting a sending provider

Connecting a sending provider

RadarSend sends your email through a sending provider (also called an ESP or MTA) that you connect with your own account and credentials. These guides walk you through getting the right credentials from each provider and connecting it in RadarSend — including delivery/bounce/complaint tracking and confirming your sending address.

Choose your provider#

The connection flow, at a glance#

Every provider follows the same four steps (the details differ per provider — see each guide):

  1. Get your credentials from the provider — create an API key with the right permission, and authenticate your sending domain (DKIM/SPF).
  2. Add the sending service in RadarSend: Settings → Sending → Sending services → + Connect a service, pick the provider, and enter your keys.
  3. Turn on tracking (webhooks) so RadarSend learns about deliveries, bounces, and spam complaints.
  4. Confirm your sending address: Settings → Sending → Senders → + Add sender, then run a test send through the service.

How the providers differ in RadarSend#

CapabilityProviders
Live connection test when you connect (RadarSend confirms your keys immediately)Amazon SES
One-click webhook setup (RadarSend configures the provider webhook for you)Amazon SES
Manual webhook setup (copy RadarSend’s webhook URL into the provider)SendGrid, Mailgun, Resend, Mailjet
Check verified domains panel (list which domains the provider has authenticated)SendGrid, Mailgun, Resend, Mailjet
Authenticate domain from RadarSend (get DKIM/SPF records in-app if a test fails)Amazon SES, SendGrid, Mailgun, Resend, Mailjet
Signed/verified webhooks (optional extra security)SendGrid, Resend (signing key); Mailgun (automatic)

For every provider, RadarSend authenticates incoming webhooks with a secret, per-account URL, so tracking is secure even without a provider-side signature.

Note

These guides describe provider dashboards (SendGrid, Mailgun, etc.) that change their menus from time to time. If a menu path looks different from what you see, the overall step is usually still the same — look for the equivalent “API Keys”, “Domains/Sender Authentication”, and “Webhooks/Event Notifications” areas.