Agent user-subscription mutations removed from the public API

The subscribe_users_to_agent and unsubscribe_users_from_agent mutations are no longer part of the public GraphQL schema. They were available in the 2027-01 release candidate, and were removed from the public schema together with their SubscribeUsersToAgentResult and UnsubscribeUsersFromAgentResult return types. The same removal applies to the 2027-04 release candidate. The mutations are now internal-only, and the stable 2026-10 version never exposed them.

Before this change, subscribe_users_to_agent took an agent_id, up to 200 user_ids and an AgentMembershipRole, and unsubscribe_users_from_agent took an agent_id and up to 200 user_ids. Requests that call either mutation against a version that no longer exposes it fail GraphQL validation.

Migration notes

If you call subscribe_users_to_agent or unsubscribe_users_from_agent against the 2027-01 or 2027-04 release candidate, remove those calls. The public schema does not currently offer a replacement mutation for managing an agent's user memberships. See the release notes for the current state of each API version.