Connecting a sending service
RadarSend sends your email through a sending service (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 sending service#
New to AWS? Set up Amazon SES from scratch takes you from a new AWS account to one that’s ready to connect.
| Sending service | Website |
|---|---|
| Amazon SES | aws.amazon.com/ses |
| SendGrid | sendgrid.com |
| Mailgun | mailgun.com |
| Resend | resend.com |
| Mailjet | mailjet.com |
What sending costs on each sending service#
RadarSend works with Amazon SES, SendGrid, Mailgun, Mailjet, and Resend. You pay your sending service directly, at its rate. Here’s what each charges for base sending at different monthly volumes.
| Sending service | 10K emails | 50K | 100K | 250K | 500K | 1M |
|---|---|---|---|---|---|---|
| Amazon SES | $1.60 | $8.00 | $16.00 | $40.00 | $80.00 | $160.00 |
| Mailgun | $15.00 | $35.00 | $90.00 | $215.00 | $400.00 | $700.00 |
| SendGrid | $19.95 | $19.95 | $34.95 | $249.00 | $499.00 | $799.00 |
| Resend | $20.00 | $20.00 | $35.00 | $200.00 | $350.00 | $650.00 |
| Mailjet | $17.00 | $37.00 | $105.00 | $250.00 | $470.00 | Contact sales |
Columns are emails per month. Prices are each service’s cheapest published plan, base sending only, without a dedicated IP, email validation, or extended log retention. Amazon SES is shown on its Essentials plan at $0.16 per 1,000 emails. Mailjet is shown from its Essential plan ($17 for 15,000 emails), since its Free and Starter plans add the Mailjet logo to every email. Mailgun’s higher volumes come from its pricing slider. Prices verified September 2026.
The connection flow, at a glance#
Every sending service follows the same four steps (the details differ per service — see each guide):
- Get your credentials from the sending service — create an API key with the permissions its guide lists, and authenticate your sending domain (DKIM/SPF) in that service’s dashboard. RadarSend doesn’t add domains to your sending service.
- Add the sending service in RadarSend: Settings→Sending→Sending services→+ Connect a service, pick the service, enter your keys, and click Connect & verify.
- Tracking (webhooks) so RadarSend learns about deliveries, bounces, and spam complaints. RadarSend sets this up during Connect & verify for every service here.
- Confirm your sending address: Settings→Sending→Senders→+ Add sender, then run a test send through the service.
How the sending services differ in RadarSend#
| Capability | Sending services |
|---|---|
| Live connection test when you connect (RadarSend confirms your keys immediately) | Amazon SES, SendGrid, Mailgun, Resend, Mailjet |
| Automatic webhook setup (RadarSend configures the service’s webhook when you connect) | Amazon SES, SendGrid, Mailgun, Resend, Mailjet |
| API key RadarSend needs | Amazon SES: the IAM policy the wizard shows · SendGrid: Restricted Access with Mail Send and Event Webhook · Mailgun: an account key with the Developer role · Resend: Full access · Mailjet: your API key and Secret Key |
| Verified sending domains section (the domains the service has, with their status and a link to each in its console) | Amazon SES, SendGrid, Mailgun, Resend, Mailjet (SendGrid’s key needs the optional Sender Authentication read permission) |
| Account status (sandbox or production, 24-hour quota, max send rate) | Amazon SES |
| Signed/verified webhooks (RadarSend checks each event came from the service) | SendGrid, Resend, and Mailgun (set up automatically) |
For every sending service, RadarSend authenticates incoming webhooks with a secret, per-account URL, so tracking is secure even without a signature from the service.
These guides describe sending service 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” and “Domains/Sender Authentication” areas.