subscription.payment_recovered
A failed renewal was settled, and the grace clock on the subscription closed.
When this fires
A renewal that had failed is paid: the rail's next charge settles, or the rail reports the subscription active again before the money reaches the ledger. Either closes the clock Revenue Recovery opened at the failure, converts every notice sent during the window and stamps recovered_at. When the window had already closed and access had been paused, the member's invite links are reissued and they are welcomed back, which subscription.access_restored reports separately.
Only a renewal of a membership that has paid before opens a clock, so this never fires for a first purchase or for a one-time rail. A charge that settles on a subscription with no open clock fires subscription.renewed alone.
Related events
subscription.access_suspended: the pause this may be undoing.subscription.access_restored: the reissued links, whenaccess_restoredistrue.payment.succeeded: the charge behind it.
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