matrix-spec-proposals/event-schemas/schema/m.room.message#m.text

---
allOf:
  - $ref: core-event-schema/room_event.yaml
description: This message is the most basic message and is used to represent text.
properties:
  content:
    properties:
      body:
        description: The body of the message.
        type: string
      msgtype:
        enum:
          - m.text
        type: string
      format:
        description: |-
          The format used in the ``formatted_body``. Currently only
          ``org.matrix.custom.html`` is supported.
        type: string
      formatted_body:
        description: |-
          The formatted version of the ``body``. This is required if ``format``
          is specified.
        type: string
    required:
      - msgtype
      - body
    type: object
  type:
    enum:
      - m.room.message
    type: string
title: TextMessage
type: object
Convert event schemas to yaml We've decided to make the event schemas YAML, so we might as well take advantage of it. (This conversion was done mostly automatically, except for: - s/null/"null"/ in m.room.member - reformat description in m.room.power_levels 8 years ago			`---`
			`allOf:`
			`- $ref: core-event-schema/room_event.yaml`
			`description: This message is the most basic message and is used to represent text.`
			`properties:`
			`content:`
			`properties:`
			`body:`
			`description: The body of the message.`
			`type: string`
			`msgtype:`
			`enum:`
			`- m.text`
			`type: string`
Document message formats as-is This is likely to later be replaced by mixins, however this is being documented now so clients aren't left in the dark. Fixes https://github.com/matrix-org/matrix-doc/issues/917 6 years ago			`format:`
			`description: \|-`
			The format used in the ``formatted_body``. Currently only
			``org.matrix.custom.html`` is supported.
			`type: string`
			`formatted_body:`
			`description: \|-`
			The formatted version of the ``body``. This is required if ``format``
			`is specified.`
			`type: string`
Convert event schemas to yaml We've decided to make the event schemas YAML, so we might as well take advantage of it. (This conversion was done mostly automatically, except for: - s/null/"null"/ in m.room.member - reformat description in m.room.power_levels 8 years ago			`required:`
			`- msgtype`
			`- body`
			`type: object`
			`type:`
			`enum:`
			`- m.room.message`
			`type: string`
			`title: TextMessage`
			`type: object`