Payload

All webhook payloads follow a consistent top-level structure with event-specific data nested within the data object.

subscriptionIdstring

The subscription ID.

customerIdstring

The customer ID. Returns your externalId if you provided one when creating the customer, otherwise returns the Commet publicId.

statusstring

Current status — the subscription stays usable.

currentPlanobject

The plan currently in effect (id and name).

revokedPlanobject

The previously scheduled plan that will no longer take effect (id and name).

billingIntervalstring | null

The current billing interval.

revokedBillingIntervalstring | null

The previously scheduled billing interval, if the revoked change included one.

{
  "event": "subscription.plan_change_revoked",
  "timestamp": "2026-04-18T16:30:00.000Z",
  "organizationId": "org_abc123",
  "mode": "live",
  "apiVersion": "2026-05-25",
  "data": {
    "subscriptionId": "sub_1a2b3c4d",
    "customerId": "user_123",
    "status": "active",
    "currentPlan": {
      "id": "plan_pro",
      "name": "Pro"
    },
    "revokedPlan": {
      "id": "plan_starter",
      "name": "Starter"
    },
    "billingInterval": "monthly",
    "revokedBillingInterval": null
  }
}

When this fires

A subscription can only have one pending scheduled change. When a new downgrade or interval change is scheduled while another one is still pending, the old one is replaced:

subscription.plan_change_revoked fires with the plan that will no longer take effect (revokedPlan).
subscription.plan_change_scheduled fires with the new target plan.

Scheduling the exact same change again is a no-op and does not fire this event. The subscription's current plan and access are unaffected — only the pending change moves.