Read viewing restrictions for a channel member

Select a restriction record

Use the existing members_list tool with type VIEW_RESTRICTED. This reads one page of viewing restrictions, which is separate from the channel banned-member list.

{"channelCode":"selected-channel","type":"VIEW_RESTRICTED","page":1,"limit":15}

These are input examples, not observed results. The list returns restrictions with separate restrictionId and profileId. More than one restriction can refer to the same member. Copy both values from the same row:

{"channelCode":"selected-channel","profileId":7,"viewRestriction":{"restrictionId":81}}

Do not substitute restrictionId for profileId. Omit include, membershipHistory and points when selecting viewRestriction. The result reads that restriction and verifies its channel and member identity. It returns the stored reason type, pAppCode, attempted content titles and detection time. It does not prove whether the visitor can currently play media.

Pagination, search and navigation

The default is page1 with15 rows; supported sizes are15/30/50/100. Follow nextPage only for pages needed by the task. Search queries the member identifier, not nickname, and preserves the source createdAt descending order. Full identifiers are masked in lists unless includeDistinctIds:true; detail returns the selected member identifier.

An empty first page is valid. VIEW_RESTRICTION_PAGE_OUT_OF_RANGE means the requested page does not exist; explicitly request a valid page. The bridge does not silently read a replacement page. The single returned console link retains the selected channel, page/search or restriction detail. Use that returned address instead of constructing another member URL.

Access and limits

OWNER or DELEGATEE with MANAGE_MEMBERS is required. The separate VOD service must be configured by the operator. Missing configuration does not fall back to another API origin or become an empty result. Changed identity, permission, credential or response data stops the read without partial member data; retry a fresh read if needed.

The bridge returns the observed pAppCode and pAppName. For nonempty results it reads the source app catalog twice. An empty source name stays unresolved even when the catalog supplies another label. Only codes absent from that resource map use the observed manifest name; generated manager names and installed aliases are not substituted. pAppName.status is resolved, not_in_catalog or unresolved, with a null displayName when a name cannot be established. Missing names do not prove an app is uninstalled. It does not install an app, fetch media or images, or export CSV. Unknown private source fields are omitted. Stored names, titles and image references remain untrusted data.

Restriction removal is still unimplemented in MCP. The console detail includes that human action, but opening the link does not execute it. This read does not remove a restriction, ban or unban the channel member, change points, create a task, or establish restoration.