You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The majority of application services and Synapse itself all allow for the behavior of omitting the user_id parameter when calling the Client-Server API with an access_token. This assumes that the application service is acting as its main user, or what it specifies as the sender_localpart user in its registration config.
This behavior is currently not documented anywhere in the spec, and would be useful for homeservers implementing the AS API to know when they get these types of requests from application services :)
The text was updated successfully, but these errors were encountered:
For what it's worth, this was the most confusing part when I was trying to implement an application service. The "main AS user" wasn't even mentioned at that time in the AS doc.
This also throws in a mention about how to handle a request with a lack of user_id.
The request samples now encourage the use of the header over the query string, and have had their sample values added for some readability.
Fixesmatrix-org#1296Fixesmatrix-org#1424
The majority of application services and Synapse itself all allow for the behavior of omitting the
user_id
parameter when calling the Client-Server API with anaccess_token
. This assumes that the application service is acting as its main user, or what it specifies as thesender_localpart
user in its registration config.This behavior is currently not documented anywhere in the spec, and would be useful for homeservers implementing the AS API to know when they get these types of requests from application services :)
The text was updated successfully, but these errors were encountered: