docs-matrix-spec/api/identity
Travis Ralston 88b35d1be5 Clarify how third party invites work
This adds several diagrams to the Client-Server API about how invites
are handled, including what the server is expected to do. This helps
implementors know what they are supposed to do in the common cases,
and infer where needed to get the more complex cases correct.

Although lacking in some areas, this is how third party invites work
today.

A link to the now-improved client-server documentation for third party
invites has been added to the server-server specification. The existing
server-server specification needed no further changes on the subject.

Fixes https://github.com/matrix-org/matrix-doc/issues/1366
2018-08-13 16:29:50 -06:00
..
associations.yaml convert IS endpoints to Swagger (#1427) 2018-08-10 16:21:06 -04:00
email_associations.yaml convert IS endpoints to Swagger (#1427) 2018-08-10 16:21:06 -04:00
invitation_signing.yaml convert IS endpoints to Swagger (#1427) 2018-08-10 16:21:06 -04:00
lookup.yaml Supply operationId for freshly added IS and AS operations 2017-11-15 07:53:36 +09:00
ping.yaml Add IS ping endpoint 2018-02-27 17:54:42 +01:00
pubkey.yaml Clarify how third party invites work 2018-08-13 16:29:50 -06:00
store_invite.yaml convert IS endpoints to Swagger (#1427) 2018-08-10 16:21:06 -04:00