Risu Mail Documentation
Complete user guide
Use this documentation hub to onboard teams, integrate every API endpoint, configure hosted forms, and operate production-safe mail + OTP workflows. Every API reference page includes code examples for all supported programming languages.
Documentation Map
Getting started
Environment setup, first key, and production checklist.
Authentication
Key scopes, public token rules, and header standards.
Mail API guide
Queue sends, template sends, and status tracking.
OTP guide
Instant OTP, verifications export, and hardening.
Hosted forms
Create forms, embed codes, and anti-spam limits.
Error handling
Status codes, retry strategy, and observability.
Quickstart
5-minute setup for keys, sends, and testing.
SMTP configuration
Host, ports, and client compatibility guidance.
SendGrid migration
Move from SendGrid with endpoint mapping.
Quick start in 60 seconds
Paste one of these snippets to verify your API key and mail queue in any supported language.
curl -X POST "https://risumail.risu.in/api/v1/templates/send-test" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"to":["hello@example.com"]}'Mail and OTP architecture
- Mail API endpoints queue email for worker delivery and status tracking.
- Template endpoints provide reusable subject/body logic with variable interpolation.
- List endpoints provide paginated operational visibility for support and dashboards.
- Instant OTP endpoints send in-request and support public token auth for client-side use.
- Verification endpoints mark OTP sessions as consumed and return verified=true on success.
- Verification list endpoints are designed for analytics exports and audit trails.
- Hosted form routes are public and enforce validation, anti-spam checks, and plan limits.
Authentication and scope model
Use mail_api keys for mail/template routes and server_otp keys for backend OTP + email verification routes. Public OTP tokens can access instant OTP routes with extra allowlist and secret checks.
Open full authentication guideFull API reference
Open endpoint-by-endpoint pages for complete request and response contracts, status codes, and all-language code demos.
Browse API reference pagesFailure handling
Handle 4xx as caller or payload issues, 429 as rate or quota pressure, and 5xx as transient infra failures. See retry and alerting guidance in the dedicated error guide.
Open error handling guideStart building with Risu Mail
Use API docs for implementation and register a free account when you are ready to run real sends.