Plan soft-deleted (removed from the catalog).
This is the final event you will receive for the given plan id.
When this fires
The plan is removed from the project. It is soft-deleted: the row is retained with deleted_at set, so subscription rows that reference it are untouched and continue to honor their existing term. Only deletions made through the REST API (DELETE /v1/projects/{project}/plans/{plan}) emit this event; deleting a plan from the creator dashboard does not.
Caveats
- Reads of the plan after this event return 404. Existing subscriptions continue to reference the plan id internally.
- Deleting a plan makes no call to the payment providers. Catalog entries previously created by the plan sync (Stripe prices, PayPal plans, and so on) remain active at the provider and must be archived there manually.
Related events
- plan.deactivated: typical predecessor.
- plan.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.