Frequently asked questions
Answers to common questions about Mailpipe, email configuration, and troubleshooting.
Mailpipe is a developer-focused email infrastructure platform. It gives you a programmable inbox — receive, send, and manage email via API, webhooks, and a modern web interface. Think of it as "your inbox, your database."
Mailpipe is a full email client + API platform. While SendGrid and Resend focus on transactional sending, Mailpipe also handles receiving, storage, routing, and provides a Gmail-like web interface. You can actually use Resend, SendGrid, Postmark, or Mailgun as your sending provider under the hood.
Mailpipe is $14/month for the standard plan, which includes 1,000 emails/day and full API access. See our pricing page for details.
Add your domain in Settings → Domains, then configure DNS records (MX, SPF, DKIM). See our domains guide for step-by-step instructions.
DNS changes typically propagate within a few minutes, but can take up to 48 hours in rare cases. Most providers update within 5-30 minutes. You can check propagation status at dnschecker.org.
Mailpipe supports Resend, Postmark, SendGrid, and Mailgun as outbound email providers. Configure your provider in Settings → Domains → Provider.
Yes! You can add multiple domains to a single organization. Each domain can have its own provider configuration and mailboxes.
mp_live_* keys send real emails and access production data. mp_test_* keys are for development — they validate requests but don't actually deliver emails.
Yes! The compose modal in the inbox uses your Supabase session to authenticate. No API key needed for browser-based sending.
Standard tier: 100 emails/hour, 1,000/day. Pro tier: 1,000/hour, 50,000/day. See Rate Limits for details.
Yes! Configure webhook endpoints to receive real-time notifications for email events (received, sent, bounced, opened). See our webhooks documentation.
mx.mailpipe.devThis means the API key doesn't match the expected mp_live_* or mp_test_* format. If you're using the web interface, make sure you're logged in — the compose modal uses your session token, not an API key.