subscription.activated
Non-active subscription transitions to active.
When this fires
A subscription leaves a non-active state (trialing, paused, past-due) and transitions to active.
Required ability
project-subscription:view-any — token must carry this at mint time to subscribe an endpoint to this event.
Payload
{
"id": "evt_01HX...",
"type": "subscription.activated",
"created_at": "2026-05-18T10:05:00Z",
"api_version": "2026-05-01",
"project_id": "prj_01HX...",
"data": {
"subscription_id": "sub_01HX...",
"plan_id": "pln_01HX...",
"subscriber_id": "usr_01HX...",
"provider": "stripe"
}
}Field reference
| Field | Type | Notes |
|---|---|---|
id | string ULID | Unique event id, prefixed evt_. Use for idempotent processing. |
type | string | Always subscription.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.subscription_id | string ULID | Subscription identifier. |
data.plan_id | string ULID | Plan the subscription is on. |
data.subscriber_id | string ULID | Subscriber's project-scoped user id. |
data.provider | string | Payment provider slug (stripe, paypal, razorpay,..) or access_code. |
Caveats
- Distinct from
subscription.created:createdfires once on first persistence;activatedfires on every transition into the active state thereafter. - Trial-to-paid transitions emit both
subscription.activatedandmember.converted.
Related events
subscription.created— initial creation.subscription.trial_started,subscription.unpaused— likely predecessors.- Subscription events overview — back to family overview.
How is this guide?