LiveKit Cloud API
POST /twirp/livekit.Egress/StartRoomCompositeEgress endpoint removal
Deprecated, no dateSubscribe to LiveKit Cloud APIShare
LiveKit Cloud API has deprecated POST /twirp/livekit.Egress/StartRoomCompositeEgress without a shutdown date. It will be removed in a future release, after which affected requests fail.
Calls it hits
POST /twirp/livekit.Egress/StartRoomCompositeEgress
What to use instead of these calls
Call POST /twirp/livekit.Egress/StartEgress with a TemplateSource instead.
In LiveKit Cloud API's words
StartRoomCompositeEgress is deprecated and will be removed in a future release.
Facts
- API
- LiveKit Cloud API
*.livekit.cloud - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against LiveKit Cloud API's own pages
Questions
When does this change take effect?
LiveKit Cloud API deprecated POST /twirp/livekit.Egress/StartRoomCompositeEgress without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: LiveKit Cloud API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from LiveKit Cloud API 4
-
No date
POST /twirp/livekit.Egress/StartParticipantEgressEndpoint removal Deprecated, no date -
No date
POST /twirp/livekit.Egress/StartTrackCompositeEgressEndpoint removal Deprecated, no date -
No date
POST /twirp/livekit.Egress/StartTrackEgressEndpoint removal Deprecated, no date -
No date
POST /twirp/livekit.Egress/StartWebEgressEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.