Read channel send restriction
Operation boundary
- Caller: Trusted backend only
- Scope: Restriction for the actual source Channel; person IDs must be canonical and CMD-derived keys are invalid; login, receiving and protocol ACKs remain allowed.
- Success: Reads current Channel Slot authority; a missing person Channel returns allow/version 0, a missing non-person Channel returns 404.
- Recovery: On 503, keep the policy unknown and retry reads with backoff; unavailable authority is not evidence of allow.
GET
/channel/send_banRead one current Slot-owned send policy without returning credentials.
Query Parameters
channel_id*string
Actual source Channel ID, at most 1024 UTF-8 bytes; person IDs must be canonical and CMD-derived IDs are rejected.
Match
^\S(?:[\s\S]*\S)?$Length
1 <= length <= 1024channel_type*integer
Source Channel type; 1 denotes a canonical person Channel, 2 a group.
Range
1 <= value <= 255Response Body
application/json
application/json
application/json
application/json
{ "status": 200, "data": { "channel_id": "string", "channel_type": 1, "send_ban": 0, "send_ban_version": "string" }}