Get a message
Read one message by id — an outbound send or an inbound reply.
Authorizations
Org-scoped Norbelys API key. Create one in Settings → API keys and send it as Authorization: Bearer ak_….
Path Parameters
The resource id (path).
Response
OK
- OutboundMessage
- InboundMessage
The other party's email — the recipient on outbound, the sender on inbound.
The other party's name.
The message id.
"act_y3rgwmhkbgxxa2qzmfyrdj0e"
The linked person, if any.
"con_mfyrdj0ey3rgwmhkbgxxa2qz"
The mailbox involved, if any.
"snd_y3rgwmhkbgxxa2qzmfyrdj0e"
The message subject.
"Quick question, Ada"
RFC conversation thread id.
Outbound channel: email, call, sms, or linkedin.
email, call, sms, linkedin "email"
Message direction — an outbound send.
Machine-readable delivery failure or bounce reason; null when none was recorded. Inspect this when status is failed or bounced.
"dlq_exhausted"
A test/probe send — surfaced in the log but excluded from campaign rates.
The campaign this message belongs to, when any; null for one-off/test sends.
"prg_a2qzmfyrdj0ey3rgwmhkbgxx"
Delivery status: queued, sent, delivered, failed, bounced, or cancelled.
queued, sent, delivered, failed, bounced, cancelled "sent"
The cadence step that produced this send, when any; null for one-off sends.
"stp_mfyrdj0ey3rgwmhkbgxxa2qz"
Always "message" — identifies the resource type.
Send/receive instant (RFC 3339).
"2026-06-10T15:04:05.000Z"