API · messages

Retrieve message

GET /api/v2/inboxes/{id}/messages/{message}

Authorization

messages:read. Use a workspace-scoped bearer key or an authorized user session.

Parameters

All resource access is checked against the selected workspace and user permissions.

Name	Type	Contract
id	path · required	Resource UUID
message	path · required	Positive mailbox UID

Request

Set INBOXIT_API_KEY in your server environment. The CLI can also use an authenticated user session.

Example

curl -X GET 'https://inboxit.wtf/api/v2/inboxes/RESOURCE_UUID/messages/42' \
  -H "Authorization: Bearer $INBOXIT_API_KEY"

CLI equivalent

Use INBOXIT_TOKEN for a scoped key, or inboxit login for a user session.

Example

inboxit messages get --id RESOURCE_UUID --message 42

Response

HTTP 200. Example values are illustrative; excerpts are marked.

Example

{
  "id": "42",
  "subject": "Re: Hello",
  "from": "recipient@example.com",
  "to": "hello@mail.yourbrand.com",
  "date": "Fri, 23 Oct 2026 12:00:00 +0000",
  "message_id": "<reply@example.com>",
  "in_reply_to": "<original@mail.yourbrand.com>",
  "references": "<original@mail.yourbrand.com>",
  "received_at": "2026-10-23T12:00:00+00:00",
  "text": "Thanks!",
  "attachments": [],
  "untrusted_content": true
}

Behavior & errors

The message path parameter is a positive mailbox UID, not an outgoing email UUID. Missing message returns 404. Use raw download when exact MIME source is needed. Common errors: 400 invalid input, 401 unauthenticated, 403 insufficient permission, 404 missing/inaccessible resource, 409 conflict, 429 rate/usage limit, 503 service unavailable. See Errors & retries for recovery guidance.