billing.grace_period_warning
The creator is approaching automatic lockdown for an unpaid invoice.
When this fires
The creator's account reaches the warning milestone on its overdue clock. That milestone depends on the plan's base price: day 3 for a creator on a zero-base-price (Free) plan, whose lockdown lands on day 7, and day 23 for a paid plan, whose lockdown lands on day 30. Fires once per past-due cycle.
Read days_until_lockdown from the payload rather than assuming a fixed offset; it carries the actual remaining days for that creator's tier.
Caveats
- Each past-due cycle produces at most one
billing.grace_period_warning. If the account recovers and re-enters past_due later, a new cycle and a new warning may issue. - After lockdown the clock keeps running: a deletion warning at 53 days locked and account deletion at 60 days locked on paid/trial thresholds (3 and 7 days on Free). Neither stage emits a
billing.*webhook; they surface as notifications only.
Related events
billing.payment_failed: the chain of failed collections leading here.billing.account_locked: fires when the lockdown day arrives: 7 days after this event on a paid tier, 4 on Free or an unconverted trial.
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