Server-Server API - Revision history

Array in a Matrix at 06:00, 23 July 2024

2024-07-23T06:00:59Z

← Older revision		Revision as of 06:00, 23 July 2024
Line 1:		Line 1:
	[[Category:~~APIs~~]]		[[Category:API]]
	[[Category:Server_software]]		[[Category:Server_software]]

	[[Homeserver\|Matrix homeservers]] use Federation APIs (also known as Server-Server APIs) to communicate with one another. Homeservers use these APIs to post and query various data from other homeservers in real-time to and from one another. These APIs are implementing using HTTP secure (HTTPS) requests between independent nodes implementing the Matrix protocol, these requests are strongly authenticated on the TLS transport layer.		[[Homeserver\|Matrix homeservers]] use Federation APIs (also known as Server-Server APIs) to communicate with one another. Homeservers use these APIs to post and query various data from other homeservers in real-time to and from one another. These APIs are implementing using HTTP secure (HTTPS) requests between independent nodes implementing the Matrix protocol, these requests are strongly authenticated on the TLS transport layer.

Array in a Matrix: 8 revisions imported: Import original IM Wiki

2024-07-14T03:24:16Z

8 revisions imported: Import original IM Wiki

← Older revision		Revision as of 03:24, 14 July 2024
(No difference)

Matrix>Sininenkissa: Remove related articles

2024-01-21T14:43:43Z

Remove related articles

← Older revision		Revision as of 14:43, 21 January 2024
Line 1:		Line 1:
	[[Category:APIs]]		[[Category:APIs]]
	[[Category:Server_software]]		[[Category:Server_software]]
	~~{{Related articles start}}~~
	~~{{Related\|Federation}}~~
	~~{{Related articles end}}~~

	[[Homeserver\|Matrix homeservers]] use Federation APIs (also known as Server-Server APIs) to communicate with one another. Homeservers use these APIs to post and query various data from other homeservers in real-time to and from one another. These APIs are implementing using HTTP secure (HTTPS) requests between independent nodes implementing the Matrix protocol, these requests are strongly authenticated on the TLS transport layer.		[[Homeserver\|Matrix homeservers]] use Federation APIs (also known as Server-Server APIs) to communicate with one another. Homeservers use these APIs to post and query various data from other homeservers in real-time to and from one another. These APIs are implementing using HTTP secure (HTTPS) requests between independent nodes implementing the Matrix protocol, these requests are strongly authenticated on the TLS transport layer.

Matrix>Sininenkissa: Test related articles

2024-01-21T14:30:51Z

Test related articles

← Older revision		Revision as of 14:30, 21 January 2024
Line 1:		Line 1:
	[[Category:APIs]]		[[Category:APIs]]
	[[Category:Server_software]]		[[Category:Server_software]]
			{{Related articles start}}
			{{Related\|Federation}}
			{{Related articles end}}

	[[Homeserver\|Matrix homeservers]] use Federation APIs (also known as Server-Server APIs) to communicate with one another. Homeservers use these APIs to post and query various data from other homeservers in real-time to and from one another. These APIs are implementing using HTTP secure (HTTPS) requests between independent nodes implementing the Matrix protocol, these requests are strongly authenticated on the TLS transport layer.		[[Homeserver\|Matrix homeservers]] use Federation APIs (also known as Server-Server APIs) to communicate with one another. Homeservers use these APIs to post and query various data from other homeservers in real-time to and from one another. These APIs are implementing using HTTP secure (HTTPS) requests between independent nodes implementing the Matrix protocol, these requests are strongly authenticated on the TLS transport layer.

Matrix>Sininenkissa: update category

2024-01-21T14:15:12Z

update category

← Older revision		Revision as of 14:15, 21 January 2024
Line 1:		Line 1:
	[[Category:~~API~~]]		[[Category:APIs]]
	[[Category:Server_software]]		[[Category:Server_software]]
	[[Homeserver\|Matrix homeservers]] use Federation APIs (also known as Server-Server APIs) to communicate with one another. Homeservers use these APIs to post and query various data from other homeservers in real-time to and from one another. These APIs are implementing using HTTP secure (HTTPS) requests between independent nodes implementing the Matrix protocol, these requests are strongly authenticated on the TLS transport layer.		[[Homeserver\|Matrix homeservers]] use Federation APIs (also known as Server-Server APIs) to communicate with one another. Homeservers use these APIs to post and query various data from other homeservers in real-time to and from one another. These APIs are implementing using HTTP secure (HTTPS) requests between independent nodes implementing the Matrix protocol, these requests are strongly authenticated on the TLS transport layer.

Matrix>Ari at 18:09, 19 January 2024

2024-01-19T18:09:19Z

← Older revision		Revision as of 18:09, 19 January 2024
Line 11:		Line 11:
	EDUs and PDUs are further wrapped in an envelope called a [[Transaction]], which is transferred from the origin to the destination homeserver using the HTTP PUT request.		EDUs and PDUs are further wrapped in an envelope called a [[Transaction]], which is transferred from the origin to the destination homeserver using the HTTP PUT request.

	These requests are a base of what makes Matrix a decentralized protocol as these APIs make Federation possible. For client-to-server communication read [[Client-Server_API\|Client Server API]].		These requests are a base of what makes Matrix a decentralized protocol as these APIs make Federation possible. For client-to-server communication read [[Client-Server_API\|Client-Server API]].

Matrix>Ari: mark as server software

2024-01-19T18:03:04Z

mark as server software

← Older revision		Revision as of 18:03, 19 January 2024
Line 1:		Line 1:
	[[Category:API]]		[[Category:API]]
	[[Category:~~Client_software~~]]		[[Category:Server_software]]
	[[Homeserver\|Matrix homeservers]] use Federation APIs (also known as Server-Server APIs) to communicate with one another. Homeservers use these APIs to post and query various data from other homeservers in real-time to and from one another. These APIs are implementing using HTTP secure (HTTPS) requests between independent nodes implementing the Matrix protocol, these requests are strongly authenticated on the TLS transport layer.		[[Homeserver\|Matrix homeservers]] use Federation APIs (also known as Server-Server APIs) to communicate with one another. Homeservers use these APIs to post and query various data from other homeservers in real-time to and from one another. These APIs are implementing using HTTP secure (HTTPS) requests between independent nodes implementing the Matrix protocol, these requests are strongly authenticated on the TLS transport layer.

Matrix>Ari: mark as client software

2024-01-19T18:02:46Z

mark as client software

← Older revision		Revision as of 18:02, 19 January 2024
Line 1:		Line 1:
	[[Category:API]]		[[Category:API]]
			[[Category:Client_software]]
	[[Homeserver\|Matrix homeservers]] use Federation APIs (also known as Server-Server APIs) to communicate with one another. Homeservers use these APIs to post and query various data from other homeservers in real-time to and from one another. These APIs are implementing using HTTP secure (HTTPS) requests between independent nodes implementing the Matrix protocol, these requests are strongly authenticated on the TLS transport layer.		[[Homeserver\|Matrix homeservers]] use Federation APIs (also known as Server-Server APIs) to communicate with one another. Homeservers use these APIs to post and query various data from other homeservers in real-time to and from one another. These APIs are implementing using HTTP secure (HTTPS) requests between independent nodes implementing the Matrix protocol, these requests are strongly authenticated on the TLS transport layer.

Matrix>Ari: mark as API

2024-01-19T17:52:47Z

mark as API

← Older revision		Revision as of 17:52, 19 January 2024
Line 1:		Line 1:
			[[Category:API]]
	[[Homeserver\|Matrix homeservers]] use Federation APIs (also known as Server-Server APIs) to communicate with one another. Homeservers use these APIs to post and query various data from other homeservers in real-time to and from one another. These APIs are implementing using HTTP secure (HTTPS) requests between independent nodes implementing the Matrix protocol, these requests are strongly authenticated on the TLS transport layer.		[[Homeserver\|Matrix homeservers]] use Federation APIs (also known as Server-Server APIs) to communicate with one another. Homeservers use these APIs to post and query various data from other homeservers in real-time to and from one another. These APIs are implementing using HTTP secure (HTTPS) requests between independent nodes implementing the Matrix protocol, these requests are strongly authenticated on the TLS transport layer.

Matrix>Ari: init

2024-01-19T17:23:50Z

init

New page

[[Homeserver|Matrix homeservers]] use Federation APIs (also known as Server-Server APIs) to communicate with one another. Homeservers use these APIs to post and query various data from other homeservers in real-time to and from one another. These APIs are implementing using HTTP secure (HTTPS) requests between independent nodes implementing the Matrix protocol, these requests are strongly authenticated on the TLS transport layer.

There are main kinds of [[Federation]] between the servers:

* Persistent Data Units (PDUs): These events are broadcast from one HS to another HS to store persistent data (such as room state)
* Ephemeral Data Units (EDUs): These events are pushed between pairs of homeservers, these events are not persisted on the homeservers (such as typing notification)
* Queries: These are single request-response interactions between a given pair of servers, they are usually defined by the GET HTTP request and they are not persisted anywhere. They simple request a snapshot of state of the requested resource (such as searching in rooms)

EDUs and PDUs are further wrapped in an envelope called a [[Transaction]], which is transferred from the origin to the destination homeserver using the HTTP PUT request.

These requests are a base of what makes Matrix a decentralized protocol as these APIs make Federation possible. For client-to-server communication read [[Client-Server_API|Client Server API]].