Outgoing
Your app sends product email.
Use one API for receipts, magic links, password resets, invites, and alerts.
POST /v1/messages
{
"from": "auth@tx.example.com",
"to": ["you@example.com"],
"subject": "Your sign-in link"
}
Product email infrastructure
Send the email your product depends on. Receive replies and inbound messages in your application. Keep the delivery trail inspectable when something fails.
Outgoing
Use one API for receipts, magic links, password resets, invites, and alerts.
POST /v1/messages
{
"from": "auth@tx.example.com",
"to": ["you@example.com"],
"subject": "Your sign-in link"
}
Incoming
Use an inbox directly or forward mail into one. Linje sends your endpoint a signed payload with the message and attachments.
POST /v1/inboxes
POST https://app.example.com/inbound
{
"from": "user@example.com",
"subject": "Reply",
"attachments": [...]
}
Product boundary
Linje handles product email in both directions, then gets out of the way. Business workflows stay in your app.
Send receipts, magic links, password resets, invites, and alerts.
Turn inbound email and attachments into signed webhook events.
No campaigns, lists, open tracking, click tracking, or workflow builder.
Common jobs
Pricing
Pricing is based on messages processed each month.
One outbound email is one message. One inbound email delivered to your webhook is one message.
Contact
Linje is onboarding access directly right now. Email a short note about your app, your expected volume, and whether you need outbound email, inbound email, or both.
Best next step
Include your company name, rough message volume, and the use case you want to launch first. We will reply directly if Linje is a fit.