Skip to main content
On Configuration → Webhooks, define endpoints to receive billing events. For example, subscribe to invoice.paid when an invoice becomes paid after successful payment. Each delivery is an HTTP POST with JSON body. Your endpoint must return HTTP 200 with body success (trimmed). Otherwise UniBee retries up to about 8 times, with intervals that usually increase from about 1 minute to about 7 minutes. The authoritative event list is returned by Webhook event list. Setup, headers, signature verification, and acknowledgement rules are in UniBee webhooks.

List of webhook events

Subscription events

See Subscription status and Subscription status flow.

User events


Payment events


Refund events


Invoice events

See Invoice status and Invoice status flow.

Plan events


Implementation notes

  • Treat subscription.track* as recurring signals; do not share idempotency keys with one-off business events.
  • Before subscribing to invoice.reversed or subscription.latest_invoice.track, confirm the trigger behavior above matches your integration.
  • Field-level payload shapes follow the domain objects in each sample below and in OpenAPI reference.

Invoice WebhookEvent sample

Subscription WebhookEvent sample

User metrics WebhookEvent sample