plan.updated
Any mutable plan field changes.
When this fires
A creator edits an existing plan — pricing, name, trial length, billing cadence, eligibility filters. Active-flag transitions emit dedicated plan.activated / plan.deactivated events instead.
Required ability
project-subscription-plan:view-any — token must carry this at mint time to subscribe an endpoint to this event.
Payload
{
"id": "evt_01HX...",
"type": "plan.updated",
"created_at": "2026-05-18T10:05:00Z",
"api_version": "2026-05-01",
"project_id": "prj_01HX...",
"data": {
"plan": {
"id": "pln_01HX...",
"name": "Premium Monthly",
"price": 29.0,
"currency": "USD",
"billing_cycle": "monthly",
"trial_days": 7,
"active": true
},
"changes": {
"price": { "from": 25.0, "to": 29.0 }
}
}
}Field reference
| Field | Type | Notes |
|---|---|---|
id | string ULID | Unique event id, prefixed evt_. Use for idempotent processing. |
type | string | Always plan.updated for this event. |
created_at | ISO 8601 timestamp | Server-side emission time. |
api_version | string | Webhook API contract version. |
project_id | string ULID | Project this event belongs to. |
data.plan | object | Full post-update plan snapshot (same shape as plan.created). |
data.changes | object<string, {from,to}> | Map of fields that changed. Keys are plan attributes; values are before/after pairs. |
Caveats
- Existing subscriptions priced on the old terms are not retroactively re-priced. New checkouts use the new price; renewals follow the rules described billing docs.
- Active-flag transitions emit
plan.activatedandplan.deactivatedinstead ofplan.updated.
Related events
plan.activated,plan.deactivated— dedicated active-flag events.plan.sync_completed— fires after price changes propagate to the PSP catalog.- Plan events overview — back to family overview.
How is this guide?