Skip to main content
This operation removes multiple users from a group at once.
When members are removed from a group, the system automatically checks their product accesses:-> If the user remains a member of other groups with the same product, the access is kept.-> If the user is no longer a member of any group with this product, the access is fully deactivated.

Request headers

string
required
The service user’s API token in the Bearer YOUR_TOKEN format. The school owner issues the token in the admin panel: Manage → School → For developers → API keys — see the “Authentication” section for details.
integer
required
The numeric ID of the seller — the account the school belongs to. Copy it on the API keys page, in the Integration data → Identifiers card. The token’s permissions are checked against this ID.
integer
required
The numeric ID of the school, found in the same place as Seller-Id. The value must match the seller’s school — otherwise a 400 error with cause: "ForbiddenSchoolMismatch" is returned.
Requires authentication and the “School User Management” permission (SchoolManageUsers).

Request parameters

The maximum number of users you can remove in one request is 250. To remove more users, use several requests.
integer
required
Group ID: the groupId field from the group list.
integer[]
required
Array of numeric Exode user IDs (not the member record IDs id from the member list, but their userId). Up to 250 users per request.
If a user is not a member of the group, they are ignored. The response contains the number of members actually removed.

Response parameters

integer
required
Number of group members actually removed. Users who were not members of the group are not counted in this number.

Interaction with automatic assignment

Removal via the API is considered manual and blocks subsequent automatic assignment: for each removed user, an exclusion is created with the reason “removed from the group manually”. Assignment rules based on the org structure will no longer add the user back to this group.Exclusions are created only for corporate groups that have automatic assignment configured. To lift the block, add the user back via adding members; this clears the exclusion.
If you synchronize group membership from an external system (for example, from 1C), keep this in mind for regular exports: removing a member in one synchronization iteration permanently excludes them from automatic assignment until they are added back via the API.

Permission requirements

Removing members from a group requires the “School User Management” permission (SchoolManageUsers).
The service user must be authenticated with a token and have the appropriate access rights to the specified school.

Updated: 2026-09-25 14:33 UTC