matrix-spec-proposals/content/client-server-api/modules/third_party_networks.md

---
type: module
weight: 270
---

### Third Party Networks

Application services can provide access to third party networks via
bridging. This allows Matrix users to communicate with users on other
communication platforms, with messages ferried back and forth by the
application service. A single application service may bridge multiple
third party networks, and many individual locations within those
networks. A single third party network location may be bridged to
multiple Matrix rooms.

#### Third Party Lookups

A client may wish to provide a rich interface for joining third party
locations and connecting with third party users. Information necessary
for such an interface is provided by third party lookups.

{{% http-api spec="client-server" api="third_party_lookup" %}}
Add support for modules 4 years ago			`---`
			`type: module`
			`weight: 270`
			`---`

			`### Third Party Networks`

			`Application services can provide access to third party networks via`
			`bridging. This allows Matrix users to communicate with users on other`
			`communication platforms, with messages ferried back and forth by the`
			`application service. A single application service may bridge multiple`
			`third party networks, and many individual locations within those`
			`networks. A single third party network location may be bridged to`
			`multiple Matrix rooms.`

			`#### Third Party Lookups`

			`A client may wish to provide a rich interface for joining third party`
			`locations and connecting with third party users. Information necessary`
			`for such an interface is provided by third party lookups.`

Update content to call the new template for HTTP APIs 4 years ago			`{{% http-api spec="client-server" api="third_party_lookup" %}}`