Inbound email,
built for developers

Other providers hand you a MIME payload and walk away

Legacy inbound email webhooks POST a raw payload to your server: the full MIME message, base64-encoded attachments, all headers. You are then responsible for parsing it, decoding attachments, persisting messages, grouping threads, handling duplicates, and scaling your receiver. Behind the checkbox is a basic HTTP forwarder. Nuntly handles all of that for you.

From inbox to API in five steps

Read threads and reply via REST

No MIME parsing, no base64 decoding, no infrastructure. Access messages as structured JSON and reply with a single API call.

import { Nuntly } from '@nuntly/sdk';

const nuntly = new Nuntly({ apiKey: process.env.NUNTLY_API_KEY });

// List recent threads in an inbox
const { data: threads } = await nuntly.inbound.threads.list({
  domainId: 'dom_xxx',
  inboxId: 'inb_xxx',
  labels: ['unread'],
});

// Fetch message content (no MIME parsing required)
const content = await nuntly.inbound.messages.content('msg_xxx');
console.log(content.text);  // Plain text body
console.log(content.html);  // HTML body

// Reply to a message, linked to its thread
await nuntly.inbound.messages.reply('msg_xxx', {
  subject: 'Re: Your support request',
  html: '<p>Thanks for reaching out. Here is how we can help...</p>',
});

Everything in the inbound stack

Nuntly handles every layer of inbound email, from MX routing to AI agent assignment.

Frequently asked questions

Common questions about this topic.

Explore more