diff --git a/api/client-server/event_context.yaml b/api/client-server/event_context.yaml index 25e5ecf6..855adcce 100644 --- a/api/client-server/event_context.yaml +++ b/api/client-server/event_context.yaml @@ -67,23 +67,28 @@ paths: A list of room events that happened just before the requested event. items: - type: object - title: RoomEvent + allOf: + - "$ref": "../../event-schemas/schema/core-event-schema/room_event.yaml" + event: + description: |- + Details of the requested event. + allOf: + - "$ref": "../../event-schemas/schema/core-event-schema/room_event.yaml" events_after: type: array description: |- A list of room events that happened just after the requested event. items: - type: object - title: RoomEvent + allOf: + - "$ref": "../../event-schemas/schema/core-event-schema/room_event.yaml" state: type: array description: |- The state of the room at the last event returned. items: - type: object - title: RoomEvent + allOf: + - "$ref": "../../event-schemas/schema/core-event-schema/state_event.yaml" examples: application/json: |- { diff --git a/specification/modules/event_context.rst b/specification/modules/event_context.rst index 2f798caa..a972e6fa 100644 --- a/specification/modules/event_context.rst +++ b/specification/modules/event_context.rst @@ -9,6 +9,8 @@ specified event. This allows clients to get the context surrounding an event. Client behaviour ---------------- +There is a single HTTP API for retrieving event context, documented below. + {{event_context_http_api}} Security considerations