team.* events
Team creation, rename, deletion, and membership changes.
Team creation, rename, deletion, and membership changes. Creating a team, inviting a collaborator and changing a collaborator's role require the Growth tier or above. Withdrawal is deliberately not gated: team.member.removed, team.deleted and invitation withdrawal all still work on an account whose tier has lapsed, so those events can reach a Free or Starter account's endpoints.
Background
Example envelope
{
"id": "evt_01HX...",
"type": "team.member.joined",
"created_at": "2026-05-18T10:05:00Z",
"api_version": "2026-05-01",
"project_id": null,
"data": {
"team_id": "a83f0d51-4c92-4b7e-8615-2fd9e70a3c86",
"user_id": "2a91c4e7-6f38-4b52-8e0d-9c1a7b3f5d80"
}
}data is flat and deliberately thin: ids, plus whatever the transition itself carries. It is not a snapshot of the team or the collaborator. Read the team member endpoint for the profile, which keeps a joined member's details behind the team-member:view ability. The one exception is team.member.invited, which carries the invitee's email: an invitee has no user record to look up yet, so the id-only rule cannot apply to it.
project_id is always null for team.* events; these are account-level.
Required ability
Tokens subscribing to team.* events must carry team:view at mint time, including for the four team.member.* events. No webhook event requires team-member:invite; that ability governs sending an invitation, not receiving the event about one.
Events
team.createdA team is created, including the personal team created alongside a new account.team.updatedA team is renamed.team.deletedA team is deleted; its projects are detached, not deleted.team.member.invitedAn invitation is issued to a new collaborator.team.member.joinedAn invited collaborator accepts and joins.team.member.removedA collaborator is removed from a team by its owner.team.member.role_changedA collaborator's role within a team changes.How is this guide?
Last updated on