billing.tier_cancelled
The creator cancels their Subscriby subscription.
When this fires
The creator cancels their Subscriby tier subscription. The account remains usable until the current period ends.
This event has two distinct payload shapes depending on which side initiated the cancellation. Branch on the presence of effective_at versus subscription_id.
Caveats
- Expect this event twice for a single cancellation. The dashboard shape fires when the creator cancels; the provider shape fires later, when the period actually ends and the provider deletes the subscription. De-duplicate on
data.creator_idif you only want to act once. - Cancellation does not refund the active period; there is a no-refunds policy on creator tier billing.
- The account does not auto-lock at
effective_atunless past_due conditions also apply; it gracefully drops to the Free tier feature set.
Related events
billing.tier_downgraded: alternative path that retains paid features.billing.invoice_paid: last paid invoice before cancellation.
Ability to subscribe
A token needs this to subscribe an endpoint to the event.
Header Parameters
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
JSONWhat Subscriby posts to your endpointapplication/json
The signed JSON envelope posted to your endpoint.
The envelope every event is delivered in.
Responses
2XXAny success status
Your endpoint acknowledged the delivery. Any 2xx status within 30 seconds marks it delivered; the response body is ignored.
defaultAny other status
Any other status, a connection failure, or no answer within 30 seconds counts as a failed attempt. The delivery is retried 8 times, after 10 seconds, 30 seconds, 2 minutes, 10 minutes, 1 hour, 6 hours, 1 day, 3 days; the last failure dead-letters it, and it can be retried from the dashboard or POST /v1/webhook-deliveries/{delivery}/retry. After 20 consecutive failures the endpoint is paused until it is resumed.
How is this guide?
Last updated on