A team is deleted; its projects are detached, not deleted.
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.
Not delivered to the deleted team's endpoints. 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.
Caveats
- A team that still has collaborators cannot be deleted: the membership table's 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.
Related events
- team.created: first event in the lifecycle.
Headers
t=<unix seconds>,v1=<hex>: the HMAC-SHA256 of "<t>.<raw body>" under the endpoint's secret. Verify it before acting, and refuse a t more than 300 seconds from now. During a secret rotation a v0= signature under the previous secret may precede v1=.
The event's ULID, bare. The envelope's id is the same ULID prefixed evt_, so strip the prefix before comparing. Deduplicate on it: a retry carries the same id.
The event name, the same as the envelope's type.
Always application/json.
Always Subscriby-Webhooks/1.0.
Payload
Response
Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.
Changes
Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.