Skip to main content
A webhook is a notification Boble sends to your own server every time something meaningful happens on one of your promotions: a new sale, a cancellation, a renewal that failed, a subscription that ran out. Instead of polling Boble or refreshing a dashboard, you give us one URL per promotion and we POST you a small JSON message the moment it happens.

​
What you can do with them

A few examples of what creators wire on top of Boble webhooks:

Notify your team on every new sale

A new buyer joins your Pro membership → an automatic message lands in your Discord or Slack channel with the buyer’s name and the promotion.

Sync buyers to your email tool

A new buyer → automatically added to your Mailchimp, Brevo or ConvertKit list and tagged with the promotion they bought.

Revoke access in external tools

A subscription is canceled → the buyer loses their VIP role on your Discord or your Notion access automatically.

Push every sale to a sheet

Every sale ends up as a new row in your Google Sheets or Airtable for accounting and reporting.

​
How it works in three steps

1

You configure one URL per promotion

From your creator dashboard, attach an HTTPS URL to a promotion. That URL is where Boble will deliver every event for that promotion.
2

Boble notifies you in real time

Every change of access on the promotion triggers an event. The same events fire whether the change came from a Stripe checkout, a Stripe renewal, a dunning failure, or a manual action on your side.
3

Your service reacts

Your server (or your Zapier / Make / n8n endpoint) receives the event and does whatever you want: notify, sync, revoke, log.

​
What events you receive

EventWhen it fires
user_promotion.access_grantedA buyer just gained access to one of your promotions.
user_promotion.canceledA buyer’s access has been canceled.
user_promotion.expiredA subscription term ended and was not renewed.
user_promotion.suspendedA recurring payment failed and access is paused.
webhook.testA test event you triggered manually to verify your setup.
Each event carries the buyer, the promotion, the timing, and the new status. The full payload of every event — with a real example — is documented in Event types.

​
Good to know

Webhooks are best-effort. If your endpoint is down or your service replies with an error, Boble does not retry automatically. The failed delivery is logged and you can replay it from your dashboard whenever you want.
Your endpoint URL must use https:// and resolve to a public host. Local and private network addresses are rejected.

​
Next

Event types

The full catalog of events, what each one means, and a real payload for each.

Payload structure

What every Boble webhook delivery looks like.