Event catalog

Flexprice sends a webhook for each of the events below. Each event name links to its payload schema in the API reference, where the object under the event’s key (invoice, payment, subscription, and so on) is documented field by field. Subscribe to events per endpoint in the dashboard under Developers > Webhooks. Every payload has the same envelope:

{
  "event_type": "invoice.update.finalized",
  "invoice": { ... }
}

The SDKs export the event names as an enum and a typed model per payload. See Parsing webhook payloads with the SDK for Go, Python, and TypeScript examples.

Customer events

Event	Fires when
`customer.created`	A new customer is created
`customer.updated`	A customer is updated
`customer.deleted`	A customer is deleted

Subscription events

Event	Fires when
`subscription.created`	A new subscription is created
`subscription.draft.created`	A new draft subscription is created
`subscription.activated`	A draft subscription is activated
`subscription.updated`	A subscription is updated (quantity, billing anchor, metadata)
`subscription.paused`	A subscription is paused
`subscription.cancelled`	A subscription is cancelled
`subscription.resumed`	A paused subscription is resumed
`subscription.plan_changed`	A subscription moves to another plan in place
`subscription.phase.created`	A new subscription phase is created
`subscription.phase.updated`	A subscription phase is updated
`subscription.phase.deleted`	A subscription phase is deleted
`subscription.spend.threshold_reached`	Subscription spend crosses a threshold
`subscription.spend.threshold_recovered`	Subscription spend recovers
`subscription.line_item_spend.threshold_reached`	Line item spend crosses a threshold
`subscription.line_item_spend.threshold_recovered`	Line item spend recovers
`subscription.group_spend.threshold_reached`	Feature group spend crosses a threshold
`subscription.group_spend.threshold_recovered`	Feature group spend recovers
`subscription.renewal.due`	A renewal is coming up

Invoice events

Event	Fires when
`invoice.update.finalized`	An invoice is finalized and locked for payment
`invoice.update.payment`	An invoice payment status changes
`invoice.update.voided`	An invoice is voided
`invoice.update`	An invoice is updated
`invoice.payment.overdue`	An invoice is past its due date
`invoice.communication.triggered`	An invoice email or notification is triggered

Payment and refund events

Event	Fires when
`payment.created`	A new payment is created
`payment.updated`	A payment is updated
`payment.failed`	A payment fails
`payment.success`	A payment succeeds
`payment.pending`	A payment is pending processing
`refund.created`	A refund is planned against an invoice
`refund.succeeded`	A refund settles to the gateway or a wallet
`refund.failed`	A refund fails (gateway refunds retry into the wallet)

Credit note events

Event	Fires when
`credit_note.created`	A new credit note is created
`credit_note.updated`	A credit note is updated

Wallet events

Event	Fires when
`wallet.created`	A new wallet is created
`wallet.updated`	A wallet is updated
`wallet.terminated`	A wallet is terminated
`wallet.transaction.created`	A wallet transaction is created (top-up, deduction)
`wallet.transaction.updated`	A wallet transaction changes state (pending to completed)
`wallet.credit_balance.dropped`	A wallet’s credit balance drops below an alert threshold
`wallet.credit_balance.recovered`	A wallet’s credit balance recovers above an alert threshold
`wallet.ongoing_balance.dropped`	A wallet’s ongoing balance drops below an alert threshold
`wallet.ongoing_balance.recovered`	A wallet’s ongoing balance recovers above an alert threshold
`wallet.ongoing_balance.updated`	A wallet real-time balance changes

Feature and entitlement events

Event	Fires when
`feature.created`	A new feature is created
`feature.updated`	A feature is updated
`feature.deleted`	A feature is deleted
`feature.wallet_balance.alert`	A wallet balance tied to a feature crosses a threshold
`entitlement.created`	A new entitlement is created
`entitlement.updated`	An entitlement is updated
`entitlement.deleted`	An entitlement is deleted
`entitlement.grant.exhausted`	An entitlement grant window’s quota is used up

Checkout events

Event	Fires when
`checkout.session.initiated`	A checkout session is created and a payment URL returned
`checkout.session.completed`	Payment confirmed; subscription active, invoice finalized
`checkout.session.failed`	Payment fails or the provider cancels the link
`checkout.session.expired`	A checkout session times out unpaid

Usage ingestion events

Event	Fires when
`event.rejected`	A usage event matched no meter and was dropped

How alert events pair up

Threshold events come in pairs. A threshold_reached or dropped event fires when a value crosses the configured line, and the matching recovered event fires when it crosses back. Configure the thresholds under spend alerts, wallet low balance alerts, and feature wallet balance alerts. event.rejected is the one event about ingestion itself. It fires when a usage event is accepted with 202 but cannot be metered, most often because event_name matches no feature or external_customer_id matches no customer. Subscribe to it in every environment; it is the only push signal that usage is being dropped. See Troubleshooting usage events.

Which events to start with

Goal	Subscribe to
Mirror invoice state into your app	`invoice.update.finalized`, `invoice.update.payment`, `invoice.update.voided`, `invoice.payment.overdue`
React to payment outcomes	`payment.success`, `payment.failed`, `refund.succeeded`
Provision and deprovision access	`subscription.activated`, `subscription.plan_changed`, `subscription.cancelled`, `entitlement.updated`
Warn customers about credits	`wallet.credit_balance.dropped`, `wallet.credit_balance.recovered`
Catch metering mistakes early	`event.rejected`

Developers

Customer events

Subscription events

Invoice events

Payment and refund events

Credit note events

Wallet events

Feature and entitlement events

Checkout events

Usage ingestion events

How alert events pair up

Which events to start with

Set up an endpoint

Webhook Events in the API reference

​Customer events

​Subscription events

​Invoice events

​Payment and refund events

​Credit note events

​Wallet events

​Feature and entitlement events

​Checkout events

​Usage ingestion events

​How alert events pair up

​Which events to start with

Set up an endpoint

Webhook Events in the API reference

Customer events

Subscription events

Invoice events

Payment and refund events

Credit note events

Wallet events

Feature and entitlement events

Checkout events

Usage ingestion events

How alert events pair up

Which events to start with