Forward a raw JMAP method-call request to the mailbox's own Stalwart principal
A thin tenant-isolation proxy: resolves which of the caller's mailboxes to act as, then forwards the request to Stalwart's JMAP endpoint authenticated as that mailbox (HTTP Basic), rewriting any client-supplied accountId in each method call to the resolved principal's own account id (defense in depth — Stalwart's own per-principal auth is the real isolation boundary).
Request
- Base URL: https://mbag.ai/api
- URL: https://mbag.ai/api/v1/jmap
- Auth: HTTP bearer
Request body
A raw JMAP request object per RFC 8620 (using, methodCalls, optional createdIds) — not modeled here; see RFC 8620 (core) and RFC 8621 (mail). Each methodCalls entry may be given as JMAP's native [name, arguments, id] triple, or as {"name":...,"arguments":...,"id":...} objects, which are transformed into triples before forwarding. An optional top-level _mailbuttons object — {"account": "<email or mailbox id>"} — selects which of the caller's mailboxes to act as when the API key owns more than one; it is stripped before forwarding and never reaches Stalwart.
Response
The JMAP response forwarded verbatim from Stalwart on success (methodResponses etc., per RFC 8620) — not modeled here.
Changes
No recorded changes to this operation across all 1 revision of this API.