docs-matrix-spec/api/client-server/definitions
Travis Ralston 2ac80d38d7 Document the /publicRooms endpoint for federation
This intentionally doesn't document the third party network aspect of the endpoint. This is scheduled for a later area for dealing with third party network/IDs and is reported as https://github.com/matrix-org/matrix-doc/issues/1476

The client-server response has been broken out to a shared file: both the client-server and server-server /publicRoom endpoints return the same thing, with slightly different inputs.

The inputs (and behaviour) are based upon the docstring here: 43ecfe0b10/synapse/federation/transport/server.py (L583-L612)
2018-08-03 11:23:44 -06:00
..
errors Spec retry_after_ms on ratelimit errors 2018-07-12 09:28:30 -06:00
auth_data.yaml
auth_response.yaml
client_device.yaml Device management API 2016-10-12 17:26:01 +01:00
device_keys.yaml Key management APIs (#894) 2017-04-20 16:51:42 +01:00
event-schemas
event.yaml Be clear that event_id is not applicable everywhere 2017-11-09 15:28:44 +01:00
event_batch.yaml
event_filter.yaml
public_rooms_response.yaml Document the /publicRooms endpoint for federation 2018-08-03 11:23:44 -06:00
push_condition.yaml
push_rule.yaml
push_ruleset.yaml
room_event_filter.yaml
security.yaml Remove references to refresh tokens and tokenrefresh 2016-10-03 17:05:56 +01:00
sync_filter.yaml
timeline_batch.yaml Minor grammar fix. 2018-02-13 18:55:36 -08:00