There are a lot of reasons, but the short list is... • Reduce code complexity • Deeper analytics & tracking • Less resource consumption • Better UX APIs Overview
Anything (almost) you can do from the SendGrid dashboard, you can do from the Web API • Edit profile / account information • Add new Incoming Parse endpoints • Retrieve stats • Manage lists (Bounces, Blocks, Unsubscribes, etc.) • Add / Remove filters (apps)
HTTP instead of SMTP? (Don’t worry, this is a really common question) A: Normally, you won’t have to. Unless... • Your ISP is blocking common SMTP ports • There is high latency between your app and SendGrid • Difficult to install / configure SMTP drivers • Simplicity for developers
User sends an email to *@yourapplication.com 2. SendGrid parses the email and attachments 3. You receive a JSON POST to your application Inbound Parse Webhook
MX 0 mx.sendgrid.net 3. Return a 200 status code from your application 1. Configure your hostname and URL settings http://sendgrid.com/developer/reply Inbound Parse Webhook
Time to Read Opened - Last Click = Time Spent Reading Processed - Delivered = SendGrid Delay For example: Opened + Clicks - (Click ∩ Opened) = Unofficial Clicks