Domain inboxes
A practical place to receive mail.
Create addresses such as hello@ or support@ for a project. They are a simple starting point, not a replacement for a full business email suite.
Project email
The mail a hosted project needs. No detour.
Start with practical domain inboxes, then send app and site mail through a verified transactional API. The two jobs are related, but they are not the same thing.
Send an emailverified domain
curl -X POST https://hostlittle.com/api/v1/email/send \
-H "Authorization: Bearer hl_email_..." \
-H "Content-Type: application/json" \
-d '{"from":"[email protected]","to":"[email protected]","subject":"Welcome"}'Two useful lanes
Receive project mail. Send application mail.
Transactional API
Send the mail your app creates.
Use scoped API keys for password resets, receipts, alerts, invites, and contact-form messages. Review delivery activity in the hosting portal.
Before you send
A few things that should be explicit.
- Verify the sending domain
- A custom API from address needs verified transactional sending DNS.
- Keep the two layers clear
- A mailbox alone does not unlock transactional API sending.
- Know the guardrail
- Extra sends are $0.5/1,000 after the plan allotment, within the monthly spend cap.
Keep project email close to the deployment.
Start at $10/mo with a fixed resource pool, Git deploys, and practical help when a launch needs it.