dcc1f4adee
* keys.yml: fix one_time_keys object contents The alternatives previously listed under two additionalProperties levels are actually one _more_ level deeper; we still can't define them in a formal way before moving to OpenAPI 3 but at least let's be honest and say there's always a dict where there's always a dict. Also, since the same data structure is used in three places now, at least give it a name, and document the actual definition (once) separately (not using it now because it's OpenAPI 3). * Changelog
24 lines
838 B
YAML
24 lines
838 B
YAML
---
|
|
title: OneTimeKeys
|
|
type: object
|
|
description: |-
|
|
One-time public keys. The names of the properties should be in the format
|
|
`<algorithm>:<key_id>`. The format of the key is determined
|
|
by the [key algorithm](/client-server-api/#key-algorithms).
|
|
additionalProperties:
|
|
oneOf:
|
|
- type: string
|
|
- type: object
|
|
properties:
|
|
key:
|
|
type: string
|
|
description: The key, encoded using unpadded base64.
|
|
signatures:
|
|
type: object
|
|
description: |-
|
|
Signature for the device. Mapped from user ID to signature object,
|
|
containing mapping from _key signing identifier_ to the signature
|
|
(see also: https://spec.matrix.org/v1.2/appendices/#signing-json)
|
|
additionalProperties:
|
|
type: object
|
|
required: ['key', 'signatures']
|