project.* events

Project hard-deleted. Final event from that project.

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 *.deleted events. 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.
postWebhookproject.deleted

Headers

SB-Signaturestring required

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=.

SB-Event-Idstring required

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.

SB-Event-Namestring required

The event name, the same as the envelope's type.

Content-Typestring required

Always application/json.

User-Agentstring required

Always Subscriby-Webhooks/1.0.

Payload

idstring required

A ULID unique to the event, prefixed evt_. Every retry carries the same id, so it is the key to deduplicate on.

type'project.deleted' required

The event name, always project.deleted here.

created_atstring date-time required

When the event was emitted, server time, ISO 8601.

api_versionstring required

The contract version of the payload shape, 2026-05-01 today. A breaking change to a shape ships under a new version.

project_idstring uuid nullable required

The project the event belongs to; null for team-scoped and billing events.

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.