Rasel MailChoose the right integration
Two separate paths: send website email or read an owner-authorized mailbox.
Editorial update: October 30, 2026In this guide
Which service do you need?
| Need | Integration | Authentication |
|---|---|---|
| Order confirmations, verification or password recovery for your site | Website-email HTTP API | Project key bound to a domain |
| Read a customer’s messages and attachments | OAuth with mail.read | Owner consent and access tokens |
Current capabilities
- A paid subscription is required. Website email also needs a ready custom domain and current sending quota.
- The sending API accepts text and HTML; this version does not accept attachments or provide an SMTP gateway or delivery webhooks.
- OAuth is read-only; it is not a substitute for a sending key, and sending keys cannot read a mailbox.
- Your application generates and validates verification codes and reset links; Rasel Mail transports the message.
Before your first integration
Start with non-sensitive test content and keep secrets on your application server. These examples use example.com domains and illustrative identifiers. No real keys are embedded and no SDK is required; ordinary HTTP requests are sufficient.