project.deleted
Project hard-deleted. Final event from that project.
This is the final event you will receive for the given project_id. Stop
emitting requests against this project after delivery.
When this fires
A project is hard-deleted by the creator. The project row and dependent data are removed; this is the final event you will receive for that project_id.
Required ability
project:view-any — token must carry this at mint time to subscribe an endpoint to this event.
Payload
{
"id": "evt_01HX...",
"type": "project.deleted",
"created_at": "2026-05-18T10:05:00Z",
"api_version": "2026-05-01",
"project_id": "prj_01HX...",
"data": {
"project": {
"id": "prj_01HX..."
}
}
}Field reference
| Field | Type | Notes |
|---|---|---|
id | string ULID | Unique event id, prefixed evt_. Use for idempotent processing. |
type | string | Always project.deleted for this event. |
created_at | ISO 8601 timestamp | Server-side emission time. |
api_version | string | Webhook API contract version. |
project_id | string ULID | Project this event belongs to. |
data.project.id | string ULID | Project identifier; matches the top-level project_id. |
Caveats
- After this event, the project's API endpoints will respond
404. Treat the row as gone. - Dependent rows (plans, subscriptions, resources) cascade but do not fan out their own
*.deletedevents — handle the project-level cleanup once. - Webhook subscriptions targeting only this project should be torn down on your side; the platform stops emitting events for it.
Related events
project.archived— typical predecessor.project.created— first event in the lifecycle.- Project events overview — back to family overview.
How is this guide?