team.deleted
Team deleted; cascading project deletes fire separately.
project_id is always null for team events. This is the final event you
will receive for the given team_id.
When this fires
A team is deleted. Cascading cleanups on team-scoped projects fire as separate events.
Required ability
team:view-any — 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": "tem_01HX...",
"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 ULID | Team that was deleted. |
data.team.name | string | Last-known display name. |
Caveats
- Subsequent project deletions and member-removed events under the team may interleave depending on queue ordering.
- The personal team is never deleted; only explicitly created teams emit this event.
Related events
team.created— first event in the lifecycle.project.deleted— cascading project removal.- Team events overview — back to family overview.
How is this guide?