# About the Member-to-Member Blocks API

The Member-to-Member Blocks API allows site members to block other members. After a member blocks another member, the 2 members no longer see each other on the site, for example in member lists and on member profiles. The blocked member isn't notified about the block.

With the Member-to-Member Blocks API, you can:

- [Block](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/members/members-v2/member-to-member-block-v1/block-member) and [unblock](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/members/members-v2/member-to-member-block-v1/unblock-member) members on behalf of the current member.
- Retrieve the [members the current member blocked](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/members/members-v2/member-to-member-block-v1/list-current-member-blocking).
- Retrieve [all blocks involving a member](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/members/members-v2/member-to-member-block-v1/list-member-blocks), in both directions.

Blocks also affect the results of the [Members API](portalId::d1972c09-74e2-4d36-a6f2-54e3310d4ad9resourceId::91c4b5cb-e090-495e-84f5-21fbb7831cdf*fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/members/members/introduction). For details, see [Integration Guide](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/members/members-v2/member-to-member-block-v1/integration-guide).

## Before you begin

It's important to note the following points before starting to code:

- A site must have the [Wix Members Area](fallback::https://www.wix.com/app-market/web-solution/members-area) installed from the App Market.
- Block Member, Unblock Member, and List Current Member Blocking act on behalf of the current member, so they must be called with a site member identity.
- Each pair of members can have a single block. A member can't block a member who has already blocked them.
- A member can remove only blocks they created. A blocked member can't remove a block.
- Blocks can't involve the site owner or site contributors. When a member becomes the site owner or a contributor, all blocks involving them are removed.

## Use cases

- [Let members manage their blocked list](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/members/members-v2/member-to-member-block-v1/sample-flows#let-members-manage-their-blocked-list)
- [Hide content from blocked members in a custom feed](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/members/members-v2/member-to-member-block-v1/sample-flows#hide-content-from-blocked-members-in-a-custom-feed)

## Terminology

- **Member**: A person who signed up to a site's Members Area.
- **Block**: A relationship in which 1 member hides another member from themselves. The 2 members can no longer see each other on the site.
- **Blocking member**: The member who created the block.
- **Blocked member**: The member the block was created on.

@sdk_package_setup

# Member-to-Member Blocks: Integration Guide

This article explains how member-to-member blocks affect the results of the [Members API](portalId::d1972c09-74e2-4d36-a6f2-54e3310d4ad9resourceId::91c4b5cb-e090-495e-84f5-21fbb7831cdf*fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/members/members/introduction), and how to handle blocks in your own app.

## How blocks affect the Members API

When a Members API method is called with a site member identity, the results take the current member's blocks into account. With any other identity, such as a Wix user or app identity, blocks don't affect the results.

- [List Members](portalId::d1972c09-74e2-4d36-a6f2-54e3310d4ad9resourceId::c2c7e954-db95-4415-b007-b20819f79374slug::list-members*fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/members/members/list-members) and [Query Members](portalId::d1972c09-74e2-4d36-a6f2-54e3310d4ad9resourceId::c2c7e954-db95-4415-b007-b20819f79374slug::query-members*fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/members/members/query-members) don't return members who blocked the current member or who the current member blocked.
- [Get Member](portalId::d1972c09-74e2-4d36-a6f2-54e3310d4ad9resourceId::c2c7e954-db95-4415-b007-b20819f79374slug::get-member*fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/members/members/get-member) returns an error when the requested member is involved in a block with the current member:
  - If the requested member blocked the current member, the method returns a `NOT_FOUND` error, as if the member doesn't exist.
  - If the current member blocked the requested member, the method returns a `NOT_FOUND` error with the application code `MEMBER_TO_MEMBER_BLOCKED`.

## Handle blocks in your app

If your app shows members or member-generated content, apply the same rule as the Members Area: neither member in a block should see the other or their content.

- To check blocks for a specific member, call [List Member Blocks](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/members/members-v2/member-to-member-block-v1/list-member-blocks). It returns blocks in both directions, so you don't need to check each direction separately.
- To show the current member who they blocked, call [List Current Member Blocking](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/members/members-v2/member-to-member-block-v1/list-current-member-blocking).
- A block doesn't notify the blocked member, so don't show the blocked member anything that reveals the block.

# Member-to-Member Blocks: Sample Flows

This article presents possible use cases and corresponding sample flows that you can support. It provides a useful starting point as you plan your implementation.

## Let members manage their blocked list

Members who block others may later want to review who they blocked and undo a block. For example, a community site can offer a "Blocked members" page in the member's account settings.

To let members manage their blocked list:

1. Call [List Current Member Blocking](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/members/members-v2/member-to-member-block-v1/list-current-member-blocking) with the current member's identity, and save the returned `blockedMemberIds`.
1. Call [Query Members](portalId::d1972c09-74e2-4d36-a6f2-54e3310d4ad9resourceId::c2c7e954-db95-4415-b007-b20819f79374slug::query-members*fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/members/members/query-members) with a Wix user or app identity, filtering by the saved IDs, to retrieve each blocked member's name and profile photo for display.
1. When the member selects a blocked member to unblock, call [Unblock Member](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/members/members-v2/member-to-member-block-v1/unblock-member) with the current member's identity, passing that member's ID as `memberId`.

## Hide content from blocked members in a custom feed

If your app shows member-generated content, such as posts or comments, it should respect blocks the same way the Members Area does. Neither member in a block should see content from the other.

To hide content from blocked members in a custom feed:

1. Before building the feed for a member, call [List Member Blocks](fallback::https://dev.wix.com/docs/api-reference/crm/members-contacts/members/members-v2/member-to-member-block-v1/list-member-blocks), passing that member's ID as `memberId`. Use `cursorPaging` to retrieve all pages.
1. Save the `memberId` of every returned block, regardless of `blockDirection`.
1. Remove content created by any of the saved members from the feed before you display it.