You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
45 lines
1.3 KiB
YAML
45 lines
1.3 KiB
YAML
---
|
|
allOf:
|
|
- $ref: core-event-schema/event.yaml
|
|
|
|
description: |-
|
|
Requests a key verification using to-device messaging. When requesting a key
|
|
verification in a room, a `m.room.message` should be used, with
|
|
[`m.key.verification.request`](#mroommessagemkeyverificationrequest) as msgtype.
|
|
properties:
|
|
content:
|
|
properties:
|
|
from_device:
|
|
type: string
|
|
description: |-
|
|
The device ID which is initiating the request.
|
|
transaction_id:
|
|
type: string
|
|
description: |-
|
|
Required when sent as a to-device message. An opaque identifier for
|
|
the verification request. Must be unique with respect to the devices
|
|
involved.
|
|
methods:
|
|
type: array
|
|
description: |-
|
|
The verification methods supported by the sender.
|
|
items:
|
|
type: string
|
|
timestamp:
|
|
type: integer
|
|
format: int64
|
|
description: |-
|
|
Required when sent as a to-device message. The POSIX timestamp in
|
|
milliseconds for when the request was made. If the request is in the
|
|
future by more than 5 minutes or more than 10 minutes in the past,
|
|
the message should be ignored by the receiver.
|
|
required:
|
|
- from_device
|
|
- methods
|
|
type: object
|
|
type:
|
|
enum:
|
|
- m.key.verification.request
|
|
type: string
|
|
type: object
|