Skip to main content
MailChannels Email API is focused on outbound email delivery. It sends messages, reports delivery events through webhooks, and helps protect your sending domains. It does not provide an inbound message content API for receiving, parsing, or storing replies.

​
Supported reply patterns

Use one of these patterns when recipients need to reply:
PatternUse it when
Real mailboxA person or team should read and answer replies in an inbox.
Shared support addressReplies should create or update support tickets through your help desk.
Dedicated inbound providerYour application needs to parse inbound message content, attachments, or reply threads.
No-reply sender plus reply_toThe visible sender should be product-owned, but replies should route elsewhere.

​
Configure reply_to

Set reply_to in your send request when replies should go to a different mailbox than the from address. 
{
  "from": {
    "email": "notifications@example.com",
    "name": "Example App"
  },
  "reply_to": {
    "email": "support@example.com",
    "name": "Example Support"
  }
}

​
What webhooks do not include

MailChannels webhooks report delivery events such as processing, delivery, bounces, drops, complaints, and unsubscribe activity. They are not inbound message webhooks and do not include reply content. If your product needs reply parsing, store the outbound request_id and message metadata in your application, then connect replies through your mailbox or inbound provider.