billing.* events
Creator's own Subscriby subscription tier — invoice, payment failures, grace periods, lockdowns.
These events describe the creator's billing relationship with Subscriby itself, not their subscribers' billing. Useful for building ops dashboards that watch for accounts heading into lockdown.
Events
billing.invoice_created
New invoice generated.
billing.invoice_paid
Invoice paid in full.
billing.invoice_overdue
Invoice marked overdue (deferred coverage).
billing.payment_failed
Recurring charge fails.
billing.grace_period_warning
7 days from lockdown.
billing.account_locked
60-day lockdown reached.
billing.tier_upgraded
Creator upgrades Subscriby tier.
billing.tier_downgraded
Creator downgrades Subscriby tier.
billing.tier_cancelled
Creator cancels Subscriby subscription.
| Event | Fires when |
|---|---|
billing.invoice_created | A new invoice is generated for the creator's Subscriby tier. |
billing.invoice_paid | An invoice is paid in full. |
billing.invoice_overdue | An invoice passes its due date without payment. |
billing.payment_failed | A recurring charge against the creator's payment method fails. |
billing.grace_period_warning | The creator is 7 days from lockdown (day 53 of the 60-day grace window). |
billing.account_locked | The account hits the 60-day lockdown. New signups blocked on my.subscriby.net/{handle}. |
billing.tier_upgraded | Creator upgrades to a higher Subscriby tier. |
billing.tier_downgraded | Creator downgrades to a lower tier. |
billing.tier_cancelled | Creator cancels their Subscriby subscription. |
See the dedicated pages above for full payload, field reference, and caveats per event.
Example payload — billing.account_locked
{
"id": "evt_01HX...",
"type": "billing.account_locked",
"created_at": "2026-05-18T10:05:00Z",
"api_version": "2026-05-01",
"project_id": null,
"data": {
"creator_id": "cre_01HX...",
"past_due_since": "2026-03-19T00:00:00Z",
"locked_at": "2026-05-18T00:00:00Z"
}
}When you'd subscribe
The typical consumer is an internal ops dashboard or Slack room — not a subscriber-facing system. Subscriby also emails the creator via the existing notification channels for every one of these events.
Required abilities
Tokens subscribing to billing.* events must carry billing:read. Writes (upgrade, downgrade, cancel) additionally need billing:manage.
How is this guide?