plan.updated
Any mutable plan field changes.
When this fires
A plan is edited through the REST API (PATCH /v1/projects/{project}/plans/{plan}): pricing, name, currency, billing cadence, eligibility filters. Edits made in the creator dashboard do not emit this event, and trial fields are only written (and only then reported) when the payload also carries kind. An active flag sent on a PATCH is reported here as an ordinary changes.active entry. The dedicated plan.activated and plan.deactivated events come only from the publish and unpublish endpoints.
Caveats
- Existing subscriptions priced on the old terms are not retroactively re-priced. New checkouts use the new price; renewals follow the billing rules.
- An
activeflag sent on a PATCH is reported here as an ordinarychanges.activeentry. The dedicatedplan.activatedandplan.deactivatedevents come only from the publish and unpublish endpoints.
Related events
plan.activated,plan.deactivated: dedicated active-flag events.plan.sync_completed: fires after price changes propagate to the provider catalog.
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
/plan.updatedHow is this guide?