Shared
ModelsExpand Collapse
Attachment identifier, typically an mxc:// URL. Use the download file endpoint to get a local file path.
Preview image URL for video attachments (poster frame). May be temporary or available only on this device; download promptly if durable access is needed.
Allowed Unicode reactions. Omitted means all emoji reactions are allowed.
Supported attachment message types and their per-type constraints, keyed by Matrix msgtype or pseudo-msgtype (for example m.image, m.video, org.matrix.msc3245.voice). Missing message types should be treated as rejected.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
Supported rich-text formatting features keyed by feature name (for example bold, inline_code, code_block.syntax_highlighting). Omitted means no formatting support is advertised.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
-2: rejected, -1: dropped, 0: unsupported, 1: partially supported, 2: fully supported.
Chat ID. Input routes also accept the local chat ID from this installation when available.
Fully qualified sender user ID. Network-backed IDs usually include the network prefix and homeserver.
Mentioned user IDs, @room, or null for legacy messages that require text scanning.
True if Beeper cannot initiate messages to this user (e.g., blocked, network restriction, or no DM path). The user may still message you.