matrix-spec/data/event-schemas/schema/core-event-schema/event.yaml

$schema: https://json-schema.org/draft/2020-12/schema

description: The basic set of fields all events must have.
properties:
  content:
    description: The fields in this object will vary depending on the type of event.
      When interacting with the REST API, this is the HTTP body.
    type: object
  type:
    description: The type of event. This SHOULD be namespaced similar to Java package
      naming conventions e.g. 'com.example.subdomain.event.type'
    type: string
required:
  - type
  - content
title: Event
type: object
[schema] Application Service Registration meta schema (#2132) 2025-08-27 08:39:05 +02:00			`$schema: https://json-schema.org/draft/2020-12/schema`

Make all the schema files yaml 2015-12-07 14:53:48 +01:00			`description: The basic set of fields all events must have.`
			`properties:`
			`content:`
			`description: The fields in this object will vary depending on the type of event.`
			`When interacting with the REST API, this is the HTTP body.`
			`type: object`
			`type:`
			`description: The type of event. This SHOULD be namespaced similar to Java package`
			`naming conventions e.g. 'com.example.subdomain.event.type'`
			`type: string`
Remove redundant 'Required' annotations from event fields 2017-11-03 18:17:59 +01:00			`required:`
			`- type`
Fix event schemas for /sync This commit clarifies the required keys for each type of event that appears in sync, fixes the core event schema not declaring 'content' as required, and includes a mention that events may not have a room_id when appearing in /sync. Fixes https://github.com/matrix-org/matrix-doc/issues/595 Fixes https://github.com/matrix-org/matrix-doc/issues/909 2018-08-27 06:22:14 +02:00			`- content`
Make all the schema files yaml 2015-12-07 14:53:48 +01:00			`title: Event`
			`type: object`