Read a single message
const url = 'https://mail.work.optidata.cloud/api/mail/mailboxes/78/messages/4186/reader';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://mail.work.optidata.cloud/api/mail/mailboxes/78/messages/4186/reader \ --header 'Authorization: Bearer <token>'The full message record plus its rendered body, in the same shape the
conversation reader returns for each of its entries. Attachments come back
with a ready-to-use, signed url — see the attachment download endpoint.
Authorizations
Section titled “Authorizations”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters”Id of the mailbox. Every mailbox the caller may use is listed in their account.
Id of the message.
Responses
Section titled “ Responses ”The message with its rendered body.
A message together with its rendered, sanitised HTML body.
object
A message as it appears inside a listing or a thread.
object
The RFC 5322 Message-ID header.
The state of a message or thread, as a set of booleans.
object
The user starred it.
It carries a calendar invitation.
A read receipt was requested.
The addresses of a message, grouped by role.
object
One participant of a message.
object
Display name, when one is known.
The role the address plays: f sender, t recipient, c carbon copy,
b blind copy, r reply-to.
One participant of a message.
object
Display name, when one is known.
The role the address plays: f sender, t recipient, c carbon copy,
b blind copy, r reply-to.
One participant of a message.
object
Display name, when one is known.
The role the address plays: f sender, t recipient, c carbon copy,
b blind copy, r reply-to.
One participant of a message.
object
Display name, when one is known.
The role the address plays: f sender, t recipient, c carbon copy,
b blind copy, r reply-to.
One participant of a message.
object
Display name, when one is known.
The role the address plays: f sender, t recipient, c carbon copy,
b blind copy, r reply-to.
One participant of a message.
object
Display name, when one is known.
The role the address plays: f sender, t recipient, c carbon copy,
b blind copy, r reply-to.
One participant of a message.
object
Display name, when one is known.
The role the address plays: f sender, t recipient, c carbon copy,
b blind copy, r reply-to.
One participant of a message.
object
Display name, when one is known.
The role the address plays: f sender, t recipient, c carbon copy,
b blind copy, r reply-to.
Left empty in listings; read the body with a reader operation.
A file carried by a message.
object
MIME part number, used to download it.
The cid an inline image is referenced by inside the body.
attachment or inline.
Position used to name a file that arrived without one.
Icon hint for a file-type badge.
Signed download link, populated by the reader operations. Use it as-is.
A file carried by a message.
object
MIME part number, used to download it.
The cid an inline image is referenced by inside the body.
attachment or inline.
Position used to name a file that arrived without one.
Icon hint for a file-type badge.
Signed download link, populated by the reader operations. Use it as-is.
The calendar invitation carried by the message, when there is one.
The folder-sharing offer carried by the message, when there is one.
Sanitised HTML, ready to render.
Example
{ "message": { "id": "4186", "participants": { "from": [ { "name": "Jane Doe", "email": "jane.doe@acme.example", "type": "f" } ], "to": [ { "name": "Jane Doe", "email": "jane.doe@acme.example", "type": "f" } ], "cc": [ { "name": "Jane Doe", "email": "jane.doe@acme.example", "type": "f" } ], "bcc": [ { "name": "Jane Doe", "email": "jane.doe@acme.example", "type": "f" } ], "replyTo": [ { "name": "Jane Doe", "email": "jane.doe@acme.example", "type": "f" } ], "sender": [ { "name": "Jane Doe", "email": "jane.doe@acme.example", "type": "f" } ], "notification": [ { "name": "Jane Doe", "email": "jane.doe@acme.example", "type": "f" } ], "resentFrom": [ { "name": "Jane Doe", "email": "jane.doe@acme.example", "type": "f" } ] }, "attachments": [ { "part": "2", "filename": "report.docx", "contentType": "application/pdf", "disposition": "attachment" } ], "inlineAttachments": [ { "part": "2", "filename": "report.docx", "contentType": "application/pdf", "disposition": "attachment" } ] }}Missing, malformed or expired authentication key.
Authentication failures use an error key rather than message.
object
Examples
No bearer token sent
{ "error": "JWT passport exception: Missing bearer token in request"}The caller may not act on this mailbox, user or resource.
Generic error envelope used by policy, binding and framework failures.
object
Human-readable description of the failure.
Examples
{ "message": "This action is unauthorized."}Rate limit exceeded. Retry after the window resets.
Generic error envelope used by policy, binding and framework failures.
object
Human-readable description of the failure.
Examples
{ "message": "Too Many Attempts."}The mail platform did not answer as expected — a folder or message that
does not exist, or a transient failure. reference is the code to quote to
support and fault_code names the underlying condition. A 503 with the
same envelope means the platform is in maintenance; retry shortly.
Failure raised by the mail platform behind the API rather than by the request itself.
object
What went wrong, phrased for the end user.
Repeats the HTTP status code.
Suggested next step.
Support reference, e.g. MZ-502.
Names the underlying condition, e.g. mail.NO_SUCH_FOLDER.
Examples
Unknown folder
{ "error": "The mail server did not answer as expected, so this action could not be completed.", "status": 502, "help": "If the problem persists, contact support and inform the error code above.", "reference": "MZ-502", "fault_code": "mail.NO_SUCH_FOLDER"}Unknown message
{ "error": "The mail server did not answer as expected, so this action could not be completed.", "status": 502, "help": "If the problem persists, contact support and inform the error code above.", "reference": "MZ-502", "fault_code": "mail.NO_SUCH_MSG"}