Cancelled subscription re-activated before `ends_at`.
When this fires
A previously cancelled subscription is reactivated before its ends_at. The subscription returns to the active state and the next billing cycle resumes.
Caveats
- Reactivation is only possible while ends_at is in the future. After expiration, a new subscription must be created instead.
- Pairs with a renewed provider subscription for paid plans; the next charge will follow normal cadence.
Related events
- subscription.cancelled: predecessor.
- subscription.expired: alternative path if reactivation does not occur.
Headers
t=<unix seconds>,v1=<hex>: the HMAC-SHA256 of "<t>.<raw body>" under the endpoint's secret. Verify it before acting, and refuse a t more than 300 seconds from now. During a secret rotation a v0= signature under the previous secret may precede v1=.
The event's ULID, bare. The envelope's id is the same ULID prefixed evt_, so strip the prefix before comparing. Deduplicate on it: a retry carries the same id.
The event name, the same as the envelope's type.
Always application/json.
Always Subscriby-Webhooks/1.0.
Payload
Response
Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.
Changes
Webhooks have no change history: a webhook is keyed by its event name rather than a path and method, so no recorded change can name it.