plan.activated
Inactive plan flipped active.
When this fires
A previously inactive plan is flipped to active and becomes purchasable on the project landing page.
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.activated",
"created_at": "2026-05-18T10:05:00Z",
"api_version": "2026-05-01",
"project_id": "prj_01HX...",
"data": {
"plan": {
"id": "pln_01HX...",
"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 ULID | Project this event belongs to. |
data.plan.id | string ULID | Plan identifier. |
data.plan.active | boolean | Always true for this event. |
Caveats
- 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.- Plan events overview — back to family overview.
How is this guide?