Mail

Import a historic email onto one of your aliases.

REST mirror of the MCP mail_import tool. Requires manage scope. Push one raw RFC 5322 message (an .eml) that never arrived at inboxy — old order mail from another mailbox, say — and it is stored, classified and embedded for mail_search exactly like inbound mail. It is an archive write: never forwarded, never digested, stored as read, and its retention clock starts at import rather than at its own Date:. Mail whose From: is your own sign-in address is accepted and flagged sent_by_user. Dedup is per user on Message-ID:. Capped per UTC calendar month (500 free / 5000 paid); 10 MiB per message.

post/v1/mail/import

Request

  • Base URL: https://api.inboxy.net
  • URL: https://api.inboxy.net/v1/mail/import
  • Auth: HTTP bearer

Query parameters

address_idstring uuid

Row id of one of your active addresses; the message is filed under it. Give this or address. Address-scoped keys must name their bound address.

addressstring

The alias by name — <local>@inboxy.net or just the local-part, case-insensitive. Alternative to address_id; if both are given they must agree.

Response

Already stored (duplicate: true); nothing changed.

message_idstring uuid required

The messages.id — the newly stored row on a 201, or the already-existing row on a duplicate, so it can be fetched either way.

message_id_rfc5322string required

The message's Message-ID:, or <inboxy-import-{sha256}@inboxy.net> synthesised from the bytes when the header is absent. Dedup key per user.

duplicateboolean required

true when this Message-ID was already stored for you; nothing was written and the quota was not spent.

sent_by_userboolean required

true when the From: is your own sign-in address — mail you sent. Stored for context; mail_reply refuses it.

Changes

No recorded changes to this operation across all 1 revision of this API.