Inbound Email API
An inbound email API for application workflows.
Give your software an address. Linje receives messages, replies, and attachments, stores the original artifacts, and delivers a signed JSON event to your webhook.
Inbox API
Provision an address for an application boundary.
curl -fsS \
-X POST \
-H "Authorization: Bearer $LINJE_PROJECT_TOKEN" \
-H "content-type: application/json" \
-d '{
"id":"documents",
"webhook-url":"https://app.example.com/linje/inbound"
}' \
https://api.linje.systems/v1/inboxesSend mail directly to the provisioned address or forward an existing address into it.
Email to HTTP
Receive the message and its attachments as one stable event.
POST https://app.example.com/linje/inbound
x-linje-inbound-id: ...
x-linje-delivery-id: ...
x-linje-timestamp: ...
x-linje-signature: sha256=...
{
"schema":"linje.inbound-email.v1",
"event-id":"...",
"inbox-id":"documents",
"email": {
"from":[{"email":"customer@example.com"}],
"subject":"Requested document"
},
"content":{"text":"Attached."},
"attachments":[
{"download":{"url":"https://api.linje.systems/..."}}
]
}Durable context
Make a reply addressable to an application object.
Create an opaque Reply-To address with immutable caller metadata. When the recipient replies, the inbound event includes the route and the context your application needs to find the right claim, order, case, or workflow.
Reliable delivery
Store first. Sign, retry, inspect, and replay.
Linje stores the raw RFC822 message and attachments before callback delivery. Webhooks are HMAC-signed and delivered at least once with automatic retry and an inspectable attempt history. Replay redelivers the same email event.
Product boundary
Email infrastructure, not workflow automation.
Linje delivers normalized email facts and durable artifacts. Your application owns extraction, triage, approvals, and every other business decision.
Next step