project.deleted
Project hard-deleted.
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.
This is the final event you will receive for the given
project_id. Stop emitting requests against this project after delivery.
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.
Header Parameters
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.
Request Body
application/json
The signed JSON envelope posted to your endpoint.
TypeScript Definitions
Use the request body type in TypeScript.
The envelope every event is delivered in.
Response Body
Example Requests
/project.deletedHow is this guide?