Documentation Index
Fetch the complete documentation index at: https://mintlify.com/sockudo/sockudo/llms.txt
Use this file to discover all available pages before exploring further.
Get Channel Users
Retrieve list of users in a presence channel
Authentication
Same authentication requirements as Trigger Event.Path Parameters
The application ID
The presence channel name (must start with
presence-)Query Parameters
Standard authentication query parameters only (auth_key, auth_timestamp, auth_version, auth_signature).
Response
Array of user objects in the presence channel
Examples
Response Examples
Terminate User Connections
Terminate all connections for a specific user
Authentication
Same authentication requirements as Trigger Event.Path Parameters
The application ID
The user ID whose connections should be terminated
Query Parameters
Standard authentication query parameters only (auth_key, auth_timestamp, auth_version, auth_signature).
Note: This endpoint typically does not have a request body. The body_md5 parameter should be omitted from authentication.
Response
true if the termination request was processed successfullyExamples
Response Examples
Rate Limiting
Same rate limit headers as single event endpoint:X-RateLimit-Limit- Maximum requests allowed per windowX-RateLimit-Remaining- Requests remaining in current windowX-RateLimit-Reset- Seconds until rate limit resetsRetry-After- Seconds to wait before retrying (when rate limited)
Error Codes
| Status Code | Description |
|---|---|
| 200 | Success |
| 400 | Bad Request (invalid channel name) |
| 401 | Unauthorized (authentication failed) |
| 404 | Application not found |
| 500 | Internal Server Error (termination failed) |
Notes
Get Channel Users
- Only works with presence channels (names starting with
presence-) - Returns all unique users currently subscribed to the channel
- User IDs come from the channel authentication data provided during subscription
- Multiple connections from the same user ID are counted only once
Terminate User Connections
- Terminates all WebSocket connections associated with the user ID
- Works across all channels the user is subscribed to
- Termination is graceful - connections receive proper close frames
- In horizontal scaling setups, termination propagates across all nodes via the adapter
- User can reconnect immediately after termination (this is not a ban)
- Useful for forcing logout, session invalidation, or security incident response