SendGrid APIs? A: There are a lot of reasons, but the short list is... • Reduce code complexity • Deeper analyCcs & tracking • Less resource consumpCon • BeNer UX
how to process your email Add extra informaCon, filters, & manipulaCons: • Define mulCple recipients • Text SubsCtuCons • Categories • Unique arguments / IdenCfiers X-SMTPAPI: { ... }
HTTP Anything (almost) you can do from the SendGrid dashboard, you can do from the Web API • Edit profile / account informaCon • Add new Incoming Parse endpoints • Retrieve stats • Manage lists (Bounces, Blocks, Unsubscribes, etc.) • Add / Remove filters (apps)
use 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
1. User sends email to *@yourapplication.com 2. SendGrid parses email & attachments 3. SendGrid POSTs the email to your application Inbound Parse Webhook
Value 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
subuser accounts Reseller API • For partners who want to integrate their pla]orm with SendGrid Mul2ple Creden2als API • Add new API keys and users to your account