Overview
Force a specified user’s device to quit/disconnect, used for administrators to kick out users or handle abnormal connections.Request Body
Required Parameters
User ID
Optional Parameters
Device identifier, used to specify a particular device type
0- App (Android, iPhone, iPad devices)1- Web (Browser, Web applications)2- Desktop (Desktop applications)
Response Fields
Operation status, returns
"ok" on successStatus Codes
| Status Code | Description |
|---|---|
| 200 | Device quit successfully |
| 400 | Request parameter error |
| 404 | User does not exist or device not connected |
| 500 | Internal server error |
Use Cases
Administrative Control
Kick Violating Users:Security Management
Suspicious Activity:Multi-Device Management
Device Limit Enforcement:Best Practices
- Logging: Always log device quit operations for audit purposes
- Notification: Notify users when their devices are forcibly disconnected
- Reason Codes: Include reason codes for different disconnect scenarios
- Rate Limiting: Implement rate limiting to prevent abuse
- Permission Check: Verify administrator permissions before allowing device quit
- Graceful Handling: Allow users to reconnect after resolving issues
Security Considerations
- Admin Only: This API should only be accessible to system administrators
- Audit Trail: Maintain detailed logs of all forced disconnections
- User Notification: Consider notifying users about forced disconnections
- Reason Documentation: Document reasons for forced disconnections
- Appeal Process: Provide a process for users to appeal disconnections

