Skip to content

Add the endpoints a MatrixRTC client needs - #22

Merged
TroyHernandez merged 3 commits into
mainfrom
matrixrtc
Oct 6, 2026
Merged

TroyHernandez merged 3 commits into
mainfrom
matrixrtc

Conversation

@TroyHernandez

Copy link
Copy Markdown
Contributor

Five endpoint functions a MatrixRTC client needs, used by mx.client's new call layer:

  • mx_openid_token(): POST /user/{id}/openid/request_token, response passed through whole (a relying party expects the object as is).
  • mx_rtc_transports(): GET /_matrix/client/unstable/org.matrix.msc4143/rtc/transports; empty list when the server lacks the endpoint.
  • mx_rtc_livekit_token(): POST <service>/sfu/get at a LiveKit JWT service with {room, openid_token, device_id}, returns {url, jwt}. Verified against lk-jwt-service 0.7.0.
  • mx_room_state(): a room's full current state, for per-device state such as call memberships.
  • mx_well_known_client(): https://<server>/.well-known/matrix/client, NULL when absent.

Tests mock mx_http the way the existing suites do (34 new expectations, 242 total). R CMD check: 0/0/0. Version 0.3.1.1.

🤖 Generated with Claude Code

mx_openid_token() requests the OpenID token a LiveKit JWT service
checks with the homeserver; mx_rtc_transports() reads the MSC4143
transport list; mx_room_state() returns a room's full current state so
per-device call memberships can be found; mx_well_known_client() reads
a server's client discovery document.
@TroyHernandez
TroyHernandez merged commit 9fb537d into main Oct 6, 2026
2 checks passed
@TroyHernandez
TroyHernandez deleted the matrixrtc branch October 6, 2026 15:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant