plan.activated

When this fires

An inactive plan is flipped to active through the REST API (POST /api/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.

Required ability

project-subscription-plan:view — token must carry this at mint time to subscribe an endpoint to this event.

Payload

{
  "id": "evt_01HX...",
  "type": "plan.activated",
  "created_at": "2026-05-18T10:05:00Z",
  "api_version": "2026-05-01",
  "project_id": "7f3d1c92-8b45-4e6a-9d21-5c8e0a4b6f13",
  "data": {
    "plan": {
      "id": "c4e82f16-93a7-4d5b-b81c-6e0f27a94d3b",
      "name": "Premium Monthly",
      "price": "29.00",
      "active": true
    }
  }
}

Field reference

Field	Type	Notes
`id`	string ULID	Unique event id, prefixed `evt_`. Use for idempotent processing.
`type`	string	Always `plan.activated` for this event.
`created_at`	ISO 8601 timestamp	Server-side emission time.
`api_version`	string	Webhook API contract version.
`project_id`	string UUID	Project this event belongs to.
`data.plan.id`	string UUID	Plan identifier.
`data.plan.name`	string	Display name.
`data.plan.price`	string	Decimal amount as a string, e.g. `"29.00"`.
`data.plan.active`	boolean	Always `true` for 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.updated for non-state edits.

plan.deactivated — paired transition.
plan.created — predecessor.
Plan events overview — back to family overview.