Transactional
Transactional email sits under the lifecycle email job. Ranla sends it through one API, with official SDKs in the languages you already ship. Lifecycle email shares the same stack and suppression list, so a marketing unsubscribe never blocks a password reset.
npm install @supersend/ranla
import { Ranla } from '@supersend/ranla'
const client = new Ranla('rnl_…')
await client.emails.send({
from: '[email protected]',
to: '[email protected]',
subject: 'Reset your password',
html: '<p>Click the link to reset your password.</p>',
})Password resets, receipts, and product mail share the same stack and one suppression list as campaigns and automations. A marketing unsubscribe never blocks a reset. You can use separate sending domains for transactional and lifecycle if you want.
Call https://api.ranla.ai. Free includes transactional sends up to 3,000 a month and 100 a day on one domain. Free also includes 500 credits to chat with Ranla, drafts in all six jobs, and pull requests. Sending campaigns and Autopilot need a paid plan, from $99/mo.
Auth mail, receipts, invites, and system notices. Templates when you want them. Webhooks when delivery status matters.
When you are ready to mail signups who went quiet, automations and lifecycle email already sit on this stack. One sending stack for both, and the other five jobs run beside it.
Questions
Yes. Password resets, receipts, and product mail go out through the Ranla API. Official SDKs cover Node, Python, PHP, Ruby, and Go, plus a CLI.
Yes. Same stack, same API, and one suppression list. A marketing unsubscribe never blocks a password reset. You can use separate sending domains for transactional and lifecycle if you want.
Yes. Free includes transactional sends up to 3,000 a month and 100 a day on one domain. Free also includes 500 credits to chat with Ranla, drafts in all six jobs, and pull requests. Sending campaigns and Autopilot need a paid plan, from $99/mo.