Feature request: Helix Twitch Teams membership API (invite + remove) with Owner OAuth

API
1

Hello — feature request / API gap discussion.

Summary

Please consider public Helix endpoints, or a documented Partner/allowlist path, for Twitch Team membership invite/add and remove, authorized by the Team Owner via OAuth.

Current documented surface

As of September 2026:

  • Helix Teams exposes only GET /helix/teams and GET /helix/teams/channel
  • There is no documented Team-management OAuth scope
  • There are no Team membership EventSub subscription types
  • The Creator Dashboard already lets the Team Owner invite and remove members manually

Why this matters

We operate LCITO — Live Creator Index Team Operations — against a real Twitch Team with more than 8,500 members.

Large Teams create a significant single-owner operational bottleneck. Trusted Team managers should be able to handle routine membership operations without sharing the Owner’s Twitch password, browser session, cookies, or tokens.

Desired model

  1. The Team Owner authorizes the application once through OAuth.
  2. The application stores the Owner grant server-side.
  3. Trusted application-level Admins can trigger Team invite/remove actions.
  4. Those Admins never receive the Owner’s Twitch credentials or OAuth tokens.
  5. Twitch remains the source of truth for Team membership.

This is the same general delegation pattern Twitch already supports for channel-management operations such as moderators.

Illustrative proposal — these APIs do not currently exist

  • POST /helix/teams/members — invite/add a creator using team_id and user_id
  • DELETE /helix/teams/members — remove a creator using team_id and user_id
  • dedicated Owner-granted scope such as team:manage:members (name illustrative)

Optional EventSub types would also be valuable:

  • team.member.invite
  • team.member.add
  • team.member.remove

Concrete use case

A Team Owner connects their Team to LCITO and authorizes Team-management access once. The Owner gives a trusted operator an Admin role inside LCITO.

If a member breaks Team rules, that Admin clicks Remove. LCITO validates the Admin’s permission and, using the Owner’s protected OAuth authorization, calls the official Twitch Team removal endpoint. The Admin never receives the Owner’s Twitch credentials.

The same model applies to Invite: an Admin selects an approved creator, LCITO validates the permission, sends the official Team invitation, records the action, and later reconciles the membership.

What we are not asking for

We are not asking for permission to use private GraphQL endpoints, browser automation, session cookies, or scraping. We want a supported Twitch API path.

Questions

  • Is public Helix support for Team membership invite/remove planned or something Twitch would consider?
  • If not public, is there a Partner/allowlisted path for this capability?
  • Is there a better product/developer contact for this request beyond developers@twitch.tv?

Thanks — happy to share product context privately with Twitch staff if useful.

2

Feature requests go to uservoice not the developer forums - https://twitch.uservoice.com/forums/310213-developers

No and thats not where such a request goes anyway.

To my knowledge no.

The teams product is ancient

File a uservoice citing the request and use case

Edit: in fact I filed one back in 2020 and I think my use case broadly matches yours

https://twitch.uservoice.com/forums/310213-developers/suggestions/39703687-team-managment

Feel free to append your use case to it