Inbound email

Jumploon can receive mail for your domain, so your app can handle replies, support requests, or emails to invoices@acme.com. Each received message is stored, sent to your webhooks as an email.received event, and can be forwarded to a mailbox.

Set up a receiving host

Use a subdomain, such as inbound.acme.com, so your regular mailbox at acme.com keeps working.

In the dashboard, open Domains, choose your verified domain, and set the Inbound host (for example inbound.acme.com). Optionally set a Forward to address.
Publish the MX record the dashboard shows for that host.
Click Verify DNS.

Through the API:

curl -X PATCH https://api.jumploon.com/v3/domains/acme.com \
  -H "Authorization: Bearer $JUMPLOON_API_KEY" -H "Content-Type: application/json" \
  -d '{ "inbound_host": "inbound.acme.com", "inbound_forward_to": "team@acme.com" }'

Mail sent to any address at inbound.acme.com now arrives in your account. The inbound host must be your domain or a subdomain of it, and it can't be the same as your tracking host.

Get notified

Subscribe a webhook to email.received. The event includes the sender, recipients, subject and the message ID. Fetch the full message from the API.

Read received email

# List
curl https://api.jumploon.com/emails/receiving -H "Authorization: Bearer $JUMPLOON_API_KEY"
 
# One message, with HTML, text and headers
curl https://api.jumploon.com/emails/receiving/<id> -H "Authorization: Bearer $JUMPLOON_API_KEY"
 
# Its attachments, base64-encoded
curl https://api.jumploon.com/emails/receiving/<id>/attachments -H "Authorization: Bearer $JUMPLOON_API_KEY"
 
# Delete it
curl -X DELETE https://api.jumploon.com/emails/receiving/<id> -H "Authorization: Bearer $JUMPLOON_API_KEY"

Forwarding

With inbound_forward_to set, each message is also forwarded to that address. The copy comes from forwarding@<your domain>, with the original sender as the Reply-To, so replying goes to the right person and SPF and DKIM still pass.

Received messages also appear in the dashboard under Inbound.