This endpoint terminates a specific conference identified by its name. All participants in the conference will be disconnected immediately.
Authentication required:
X-Auth-ID - Your account ID (e.g., {auth_id})
X-Auth-Token - Your account Auth Token
Content-Type: application/json
The current conference instance ends and its members disconnect. A later call using <Conference> with the same name can create a new conference instance.
Use Cases: End scheduled meetings on time, terminate conferences due to emergencies, clean up abandoned conference rooms, administrative conference management.
Path parameters
No request body needed. Simply use the DELETE method with the conference name in the URL path.
Request Body
No request body parameters required. Send an empty JSON object.
Response
Returns an acknowledgment that the conference has been terminated.
Response - 204 No Content
What Happens:
- All participants are immediately disconnected from the conference
- The current conference instance ends. A later call using
<Conference> with the same name can create a new conference instance
- Vobiz sends exit callbacks for disconnected members when a callback URL is configured
If the conference has already ended or does not exist, you may receive an error response. Always handle 404 errors gracefully in your application.
Example Request
Hang Up Conference by Name
URL-encode conference names that contain spaces or special characters.
Common Use Cases:
- Scheduled end time: Automatically terminate meetings at their scheduled end time
- Emergency termination: End conferences immediately due to security or policy violations
- Admin control: Allow moderators to end conferences from admin panels
- Cleanup: Terminate abandoned conference rooms to free resources
- Time limits: Enforce maximum conference duration limits
- Workflow triggers: End conference when specific conditions are met
Best Practices:
- Notify participants before hanging up a conference (e.g., play announcement first)
- Track the room name in your application; the retrieve endpoint is not reliable for preflight checks
- Log conference terminations for audit trails and analytics
- Implement confirmation dialogs in admin UIs before terminating active conferences
- Handle errors gracefully - conference may have already ended naturally
- Consider using Kick Member instead if you only need to remove specific participants
Alternative: Hang Up All ConferencesIf you need to terminate all conferences at once (e.g., for system maintenance), use the Hang Up All Conferences endpoint instead. Your Vobiz account Auth ID
Your Vobiz account Auth Token