Helix API: Twitch Teams membership management (invite/remove) + EventSub

Twitch Helix currently allows applications to read Twitch Team membership, but there is no documented OAuth-authorized API for managing Team membership.

This becomes a significant operational limitation for large Twitch Teams.

We operate LCITO (Live Creator Index Team Operations) with a real Twitch Team containing more than 8,500 members. LCITO can synchronize the Team roster through Helix, provide delegated Admin/Recruiter roles, maintain audit logs, queue membership actions, and reconcile changes observed on Twitch.

However, the final Team invitation or removal must still be performed manually through the Team Owner's Twitch account.

Requested capability

We would like Twitch to consider adding official OAuth-authorized Team membership management to Helix.

Ideally this would include:

• An OAuth scope for Team membership management, such as team:manage:members
• A supported endpoint to invite a creator to a Team
• A supported endpoint to remove a creator from a Team
• Optionally, EventSub events for Team membership invitations, additions, and removals

The exact endpoint, scope, and event names should of course be determined by Twitch.

Delegated administration use case

A Team Owner should be able to authorize a third-party application through OAuth and then delegate operational work to trusted administrators inside that application.

For example:

Team Owner → OAuth authorization → Team management application → authorized Admin → invite/remove Team member

The application performs the Twitch action using the Owner's protected server-side authorization.

The delegated Admin never receives the Owner's password, browser session, cookies, access token, or refresh token.

The Owner can revoke the application's authorization at any time.

Why this matters

Large Twitch Teams can contain thousands of creators, making membership administration difficult to centralize on a single Team Owner.

An official API would enable third-party Team management tools to provide secure, revocable, and auditable delegation rather than encouraging account sharing, session sharing, browser automation, scraping, or use of undocumented endpoints.

LCITO deliberately does not use private GraphQL endpoints, browser automation, session cookies, or scraping to modify Twitch Team membership. We want to build this functionality using an officially supported Twitch API.

Helix already supports OAuth-authorized management for several channel capabilities. Extending a similar authorization model to Twitch Teams would allow developers to build safer Team-management tooling while Twitch remains the authoritative source for membership and authorization.

A production use case already exists: LCITO currently manages operational workflows around a Twitch Team with 8,500+ members, but cannot perform the final invite/remove mutation because no documented Team membership write API currently exists.

Thank you for considering official Twitch Team membership write support.