Remove join_conference command and related examples from API docs#477
Merged
Conversation
Devon-White
marked this pull request as ready for review
July 14, 2026 19:23
Contributor
hey-august
self-requested a review
July 20, 2026 13:57
join_conference command and related examples from API docs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR removes the
calling.join_conferencecommand from the Calling API reference. The command is not supported by the Calls endpoint, so its entry in the supported-commands table, its request example, and theCallJoinConferenceRequest/ConferenceStreamParamsschemas have been removed from the TypeSpec source, with the generated OpenAPI spec regenerated to match. (The SWMLjoin_conferencemethod is a separate feature and remains documented.)It also corrects the endpoint description: the previous text claimed "all async-safe RELAY methods" could be sent through the endpoint, which contradicted the finite command list. The description now states that only the listed commands are supported, notes that
dialcreates a call while the other commands act on an active one, and explains that asynchronous operations deliver results viastatus_urlwebhooks.