plan.activated
Inactive plan flipped active.
When this fires
An inactive plan is flipped to active through the REST API (POST /v1/projects/{project}/plans/{plan}/publish) or the publish_plan MCP tool, and becomes purchasable on the project landing page. Toggling a plan on from the creator dashboard does not emit this event.
Caveats
- Publishing a plan that is already active is a no-op: nothing is written and no event is emitted.
- Activation does not retroactively touch existing subscriptions on the plan; only checkout availability changes.
- Frequent flipping is permitted but produces noisy timelines; use
plan.updatedfor non-state edits.
Related events
plan.deactivated: paired transition.plan.created: predecessor.
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.activatedHow is this guide?