matrix-doc/api/client-server/notifications.yaml

134 lines
4.8 KiB
YAML
Raw Permalink Normal View History

2016-10-05 09:15:49 +00:00
# Copyright 2016 OpenMarket Ltd
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
swagger: '2.0'
info:
title: "Matrix Client-Server Notifications API"
version: "1.0.0"
host: localhost:8008
schemes:
- https
- http
basePath: /_matrix/client/%CLIENT_MAJOR_VERSION%
consumes:
- application/json
produces:
- application/json
securityDefinitions:
$ref: definitions/security.yaml
paths:
"/notifications":
get:
summary: Gets a list of events that the user has been notified about
description: |-
This API is used to paginate through the list of events that the
user has been, or would have been notified about.
operationId: getNotifications
2016-10-05 09:15:49 +00:00
security:
- accessToken: []
parameters:
2016-10-05 10:48:14 +00:00
- in: query
2016-10-05 09:15:49 +00:00
type: string
name: from
description: Pagination token given to retrieve the next set of events.
required: false
x-example: "xxxxx"
2016-10-05 10:48:14 +00:00
- in: query
type: integer
2016-10-05 09:15:49 +00:00
name: limit
description: Limit on the number of events to return in this request.
required: false
x-example: "20"
2016-10-05 10:48:14 +00:00
- in: query
2016-10-05 09:15:49 +00:00
name: only
type: string
description: |-
2016-10-05 10:21:56 +00:00
Allows basic filtering of events returned. Supply ``highlight``
2016-10-05 09:15:49 +00:00
to return only events where the notification had the highlight
tweak set.
required: false
x-example: "highlight"
responses:
200:
description: A batch of events is being returned
examples:
application/json: {
2016-10-05 09:15:49 +00:00
"next_token": "abcdef",
2016-10-05 09:32:03 +00:00
"notifications": [
{
"actions": [
"notify"
],
2016-10-05 10:15:33 +00:00
"profile_tag": "hcbvkzxhcvb",
2016-10-05 09:32:03 +00:00
"read": true,
"room_id": "!abcdefg:example.com",
2016-10-05 10:15:33 +00:00
"ts": 1475508881945,
2016-10-05 09:32:03 +00:00
"event": {
"$ref": "definitions/event-schemas/examples/m.room.message$m.text"
2016-10-05 09:32:03 +00:00
}
2016-10-05 09:15:49 +00:00
}
2016-10-05 09:32:03 +00:00
]
2016-10-05 09:15:49 +00:00
}
schema:
type: object
2016-10-05 17:53:08 +00:00
required: ["notifications"]
2016-10-05 09:15:49 +00:00
properties:
next_token:
type: string
description: |-
The token to supply in the ``from`` param of the next
``/notifications`` request in order to request more
2016-10-05 17:26:42 +00:00
events. If this is absent, there are no more results.
2016-10-05 09:15:49 +00:00
notifications:
type: array
items:
type: object
2016-10-05 17:53:08 +00:00
required: ["actions", "event", "read", "room_id", "ts"]
2016-10-05 17:26:42 +00:00
title: Notification
2016-10-05 09:15:49 +00:00
properties:
actions:
type: array
description: |-
The action(s) to perform when the conditions for this rule are met.
See `Push Rules: API`_.
items:
type:
- object
- string
2016-10-05 09:15:49 +00:00
event:
type: object
title: Event
description: The Event object for the event that triggered the notification.
allOf:
- "$ref": "definitions/event.yaml"
profile_tag:
type: string
description: The profile tag of the rule that matched this event.
read:
type: boolean
description: |-
Indicates whether the user has sent a read receipt indicating
that they have read this message.
room_id:
type: string
description: The ID of the room in which the event was posted.
ts:
2016-10-05 17:26:42 +00:00
type: integer
2016-10-05 09:15:49 +00:00
description: |-
The unix timestamp at which the event notification was sent,
2016-10-05 17:22:03 +00:00
in milliseconds.
2016-10-05 09:15:49 +00:00
description: The list of events that triggered notifications.
tags:
2016-10-05 17:26:42 +00:00
- Push notifications