Skip to main content
The Sendmux Mailbox API is for mailbox-scoped access. Use it when a client should act as a mailbox, or as one mailbox from a connected-app mailbox set, without managing team-wide resources.

Attachments

Use POST /mailbox/attachments:upload for binary files up to 7.5 MB. Send the raw bytes in the request body, then pass the returned blob_id to POST /mailbox/messages/send. Final outbound messages, including bodies, headers, and encoded attachments, must fit inside the 25 MB raw message limit.
Then send the uploaded attachment by ID:
Small inline base64 attachments are still supported on messages/send, but the upload endpoint avoids large JSON request bodies. Message metadata can include a short-lived download_url for clients that need a no-header download link. Fetch it promptly without an Authorization header. If it expires, re-read message or attachment metadata to receive a fresh URL. MCP clients should prefer mailbox_read_attachment for text-like inbound attachments and use the returned link only for binary or oversized files. Attachment downloads support byte ranges:

Next steps

Mailbox API introduction

Synchronisation