Transactional email from your app
Automated messages your app sends after an action: password resets, login codes, receipts. Send them from Loops alongside your marketing and product email, on a free tier that never expires.
What is a transactional email?
A transactional email is an automated message sent to one person after they take an action, like a password reset, login code, or receipt. Unsubscribe requirements depend on the message’s purpose and applicable law. Keep promotional content separate from essential account mail.
Can I send transactional email over SMTP?
Yes. Connect to smtp.loops.so on port 587 with STARTTLS. The username is loops and the password is a Loops API key. The message body is a JSON payload with a transactionalId, the recipient’s email, and any dataVariables, so Loops builds each email from a transactional template you published rather than from raw HTML. The Loops docs have SMTP guides for Supabase, Auth0, Laravel, Rails, and Django.
What affects transactional inbox placement?
Loops sends transactional email without open or click tracking. Authenticate your domain, send only the account message the recipient expects, and monitor delivery events. These practices support delivery but do not guarantee inbox placement.
How does Loops authenticate my domain?
Add the DNS records Loops supplies for your sending domain and configure DMARC. SPF authorizes sending systems, DKIM signs messages, and DMARC checks alignment with the visible From domain. Authentication does not guarantee inbox placement.
Can I see delivery results?
Yes. View sends, bounces, and spam complaints for every transactional email on the metrics page.
Is transactional email free?
The free tier includes unlimited contacts and up to 4,000 combined marketing and transactional sends to your first 1,000 contacts in any rolling 30-day window. It does not expire.