team.deleted

project_id is always null for team events.

An endpoint is scoped to a team, and deleting the team removes its endpoints in the same operation, so this event is not currently delivered to endpoints belonging to the deleted team.

When this fires

A team is deleted. Projects that were scoped to it are detached — their team_id becomes null and they keep running under the owner's personal scope. Nothing about them is deleted and no project.* event fires.

Required ability

team:view — token must carry this at mint time to subscribe an endpoint to this event.

Payload

{
  "id": "evt_01HX...",
  "type": "team.deleted",
  "created_at": "2026-05-18T10:05:00Z",
  "api_version": "2026-05-01",
  "project_id": null,
  "data": {
    "team_id": "a83f0d51-4c92-4b7e-8615-2fd9e70a3c86",
    "name": "Research Team"
  }
}

Field reference

Field	Type	Notes
`id`	string ULID	Unique event id, prefixed `evt_`. Use for idempotent processing.
`type`	string	Always `team.deleted` for this event.
`created_at`	ISO 8601 timestamp	Server-side emission time.
`api_version`	string	Webhook API contract version.
`project_id`	null	Always `null` — account-level event.
`data.team_id`	string UUID	Team that was deleted.
`data.name`	string	Last-known display name.

Caveats

A team that still has collaborators cannot be deleted: the team_user foreign key restricts it. Every team.member.removed for the team therefore precedes team.deleted, never follows it.
The only team that cannot be deleted is your last one; an owner with more than one team may delete whichever they like, including the team created with the account. Nothing in the payload distinguishes them.

team.created — first event in the lifecycle.
Team events overview — back to family overview.