subscription.reactivated

{ "event": "subscription.reactivated", "timestamp": "2026-06-23T14:30:00.000Z", "organizationId": "8f14e45f-ceea-4e7a-9c3d-1c2b3a4d5e6f", "mode": "live", "apiVersion": "2026-08-27", "data": { "subscriptionId": "sub_1a2b3c4d", "customerId": "user_123", "status": "active", "currentPeriodStart": "2026-05-10T00:00:00.000Z", "currentPeriodEnd": "2026-06-10T00:00:00.000Z", "name": "Acme Corp", "invoiceId": "inv_q7r8s9", "invoiceNumber": "INV-0051", "invoiceTotal": 9900, "invoiceCurrency": "usd", "provider": "stripe" } }

When this fires

A canceled subscription was reactivated through reactivate and the reactivation charge succeeded. Commet generates a fresh invoice, charges the saved payment method, and sets the status back to active with a billing period anchored to the reactivation date.

The subscription returns to active at the same time, so customer.state_changed also fires. Restore access on either event.

This is distinct from two similar events. subscription.activated fires on a subscription’s first activation. payment.recovered fires when a past_due subscription is recovered — that path keeps the original invoice and billing anchor, while reactivation issues a new invoice and resets the anchor to now.

The subscription returns on the latest version of what was bought, which must sell the subscription’s currency. If the reactivation charge declines, no event fires and the API returns a recoveryUrl the customer can use to add a new card and pay.

Body

application/json

string

required

event

string

required

Allowed value: "subscription.reactivated"

timestamp

string

required

organizationId

string

required

mode

enum<string>

required

Available options:

live,

sandbox

apiVersion

string

required

data

object

required

Show child attributes

Response

200

Return any 2xx status code to acknowledge receipt of the event.

Overview

Events

subscription.reactivated

When this fires

Body

Response

​When this fires

Body

Response

When this fires