Skip to main content
POST
Kick a conference member
Disconnect a member from a conference. Unlike Hang Up, kicking a member continues their XML execution - so you can play them a message or redirect them after they leave.
Authentication required: X-Auth-ID, X-Auth-Token, Content-Type: application/json
Kick vs Hang Up: Use Kick when you want to remove a member but play them an announcement or redirect them via XML after disconnect. Use Hang Up to terminate the call completely.

Path parameters

XML continuation example

When a member is kicked, Vobiz executes the next element in the XML. For example:

Request body

No request body required. Send an empty JSON object {}.

Examples

Response

202 Accepted
Vobiz removes the member from the room and continues the call with the next element after <Conference> in the participant’s XML response. A later join may reuse the same member ID.

Authorizations

X-Auth-ID
string
header
required

Your Vobiz account Auth ID

X-Auth-Token
string
header
required

Your Vobiz account Auth Token

Path Parameters

auth_id
string
required

Your account Auth ID

Example:

"MA_XXXXXX"

conference_name
string
required
member_id
string
required

Response

202 - application/json

Kick request accepted