archive
/
matrix-spec-proposals
mirror of https://github.com/matrix-org/matrix-spec-proposals
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Allow GET endpoint to filter on ID

Browse Source
toger5/expiring-events-keep-alive
Andrew Ferrazzutti 2 months ago
parent 1359f2b674
commit 59392f28ba
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File

3
proposals/4140-delayed-events-futures.md
Unescape Escape View File

@ -215,6 +215,9 @@ Without this parameter, both scheduled and finalised delayed events are included
Requests that set this parameter to multiple values (e.g. `?status=scheduled&status=finalised`) or an unsupported value Requests that set this parameter to multiple values (e.g. `?status=scheduled&status=finalised`) or an unsupported value
will respond with HTTP 400 and `M_UNKNOWN`. will respond with HTTP 400 and `M_UNKNOWN`.
The endpoint accepts a query parameter of `delay_id=<delay_id>` to filter the response on delayed events with a matching ID.
This parameter may be specified multiple times to filter on multiple matching IDs.
The endpoint accepts a query parameter `from` which is a token that can be used to paginate the list of delayed events as The endpoint accepts a query parameter `from` which is a token that can be used to paginate the list of delayed events as
per the [pagination convention](https://spec.matrix.org/v1.11/appendices/#pagination). The homeserver can choose a suitable per the [pagination convention](https://spec.matrix.org/v1.11/appendices/#pagination). The homeserver can choose a suitable
page size. page size.

Write Preview
Loading…
Cancel
Save