SendGrid SMTP Configuration
Use these exact values when configuring any email client or application to send through SendGrid servers.
| Parameter | Value |
|---|---|
| SMTP Host | smtp.sendgrid.net |
| SMTP Port | 587 (TLS) or 465 (SSL) |
| Encryption | STARTTLS on port 587, SSL on port 465 |
| Username | apikey (the literal string "apikey") |
| Password | Your SendGrid API Key (SG.xxxxx...) |
Note: SendGrid uses API Keys for authentication, not your account password. The username is always the literal string apikey. Generate API Keys in your SendGrid dashboard under Settings > API Keys.
Step-by-Step Setup
Follow these steps in order to configure SMTP access for SendGrid.
1. Create a SendGrid API Key
Log in to your SendGrid dashboard and navigate to Settings > API Keys. Create a new API Key with "Full Access" or "Restricted Access" including Mail Send permissions.
2. Verify Your Sender Identity
Before sending, verify a sender identity (Sender Authentication) in SendGrid. This involves verifying a From email address or domain to meet SendGrid's sender requirements.
3. Configure Your Application
Enter smtp.sendgrid.net as the SMTP host, port 587 with TLS, the username apikey, and your full API Key (starting with SG.) as the password.
4. Send a Test Message
Send an email to yourself and an external address to confirm delivery. Check your SendGrid dashboard for delivery status and any bounce events.
Common Errors and Solutions
Most SendGrid SMTP issues fall into a handful of categories. Here's how to fix them quickly.
Authentication Failed
Using your account password instead of an API Key is the most common cause. The username must be the literal string "apikey" and the password must be the full API Key starting with "SG."
Sender Not Verified
SendGrid requires sender identity verification before sending. Either verify a Single Sender Address or complete Domain Authentication in your SendGrid dashboard.
Connection Timeout
Port 587 may be blocked by your network. Try port 465 with SSL encryption as an alternative. Corporate firewalls commonly block direct SMTP on port 587.
Account Suspended
SendGrid may suspend accounts for policy violations or high bounce rates. Check your SendGrid dashboard for suspension notices and follow their remediation process to restore sending.
Best Practices for SendGrid SMTP
Keep your account secure and your messages deliverable with these recommended approaches.
Use Restricted API Keys
Instead of Full Access API Keys, create Restricted Access keys with only the Mail Send permission. This limits the blast radius if a key is compromised.
Complete Domain Authentication
Authenticate your sending domain in SendGrid to improve deliverability and enable DKIM signing. This verifies to receivers that your emails are legitimately from your domain.
Enable Webhooks for Bounces
Configure Event Webhook to receive bounce, spam, and unsubscribe events in real time. This allows your system to stop sending to invalid addresses promptly.
Monitor Your Sender Reputation
Track your SendGrid sender score and email metrics. High bounce rates and spam complaints damage your sender reputation and can lead to throttling or account suspension.
When SendGrid SMTP Needs an Alternative
SendGrid is a professional email service provider, but its SMTP relay can become expensive at high volume and lacks advanced routing features. If you're hitting SendGrid's rate limits, paying per-email fees that add up, or need more granular control over routing, a dedicated SMTP relay service with predictable pricing may be more cost-effective.
For teams needing deeper analytics, custom DKIM signing across multiple domains, and intelligent routing rules, an email API platform provides more control. Learn more about email deliverability and how to protect your sender reputation at scale.
Frequently Asked Questions
What are SendGrid's SMTP sending limits?
SendGrid's limits depend on your plan. Free accounts can send 100 emails/day. Paid plans range from 40,000 to millions per month. There are also rate limits of 1,000 emails/second on Pro plans and above.
Can I use SendGrid SMTP with a custom domain?
Yes. Complete Domain Authentication in SendGrid to verify your custom domain. Once verified, you can send from any address within that domain using your SendGrid SMTP credentials.
Why does SendGrid require sender verification?
SendGrid requires sender verification to prevent abuse and improve deliverability. Unverified senders can be suspended or have their sending privileges revoked. Complete Single Sender verification for testing or Domain Authentication for production.
My SendGrid SMTP is being rejected. What should I do?
Verify your API Key is correct and includes Mail Send permissions. Confirm your sender identity is verified. Check your SendGrid dashboard for account suspension notices. Try switching from port 587 to port 465.
Is SendGrid suitable for transactional emails?
Yes, SendGrid is well-suited for transactional email. It offers webhook event notifications, detailed analytics, and high deliverability when properly authenticated. However, costs can scale with volume compared to dedicated transactional email services.
Ready to move to reliable email infrastructure?
Start free with no card, or talk to sales for high-volume and enterprise.
Start SendingTalk to Sales