What Triggers a Webhook

In this section, you will learn about webhook trigger actions.

Overview

Use this page to map webhook events to the actions that fire them. This is useful when building integrations, automations, and support workflows.

Need the full event list and payload schemas? Use the API reference as the source of truth.

---

Transaction and units events

TransactionRegistered

Sent when a transaction is created:

• In the Admin panel

• Via API: Create a transaction

• Via transaction import

AvailablePointsAmountChanged

Sent when a member’s available units change. Common reasons include:

• Units are spent (reward purchase or spend endpoint)

• Units are added or deducted manually by an admin

• A campaign adds or deducts units

• Unit transfers are imported

• A unit transfer is cancelled: Cancel a points transfer

• Pending units are activated (automatically or manually)

• Units expire (automatically or manually)

• Units are blocked (see block endpoint) or unblocked

• Units are transferred between members (two events are sent: sender + receiver)

TransactionAssignedToCustomer

Sent when a transaction is matched to a member:

• Manually in the Admin panel

• Via API: Assign a transaction to a member

• Via import

CampaignEffectWasApplied

Sent when a campaign effect is applied to a member. This includes awarding or deducting units, granting rewards, and changing member custom attributes.

See also: Reward Flow.

PointsWillExpire

Sent X days before units expire. The value of X comes from Expiring Notifications.

WalletBalanceUpdated

Sent on every wallet balance change for a member. This includes:

• Units are spent (reward purchase or spend endpoint)

• Units are added or deducted manually by an admin

• A campaign adds or deducts units

• Unit transfers are imported

• A unit transfer is cancelled: Cancel a points transfer

• Pending units are activated (automatically or manually)

• Units expire (automatically or manually)

• Units are blocked (see block endpoint) or unblocked

• Units are transferred between members (two events are sent: sender + receiver)

---

Reward and coupon events

RewardRedemptionStatusChanged

Sent when a redeemed reward changes status:

• In the Admin panel

• Via API: Change redemption status

CustomerBoughtReward

Sent when a member receives a reward:

• Reward is assigned manually

• Reward is granted by a campaign

• Reward is purchased from the reward catalog

See also: Reward Flow.

CouponWillExpire

Sent X days before a reward coupon expires. The value of X comes from Expiring Notifications.

---

Member and tier events

CustomerRegistered

Sent when a member is created:

• In the Admin panel

• Via API: POST /api/{storeCode}/member

CustomerWasRegisteredWithoutActivation

Sent when a member is registered without activation:

• Via API: POST /api/{storeCode}/member/register

CustomerUpdated

Sent when a member profile is updated in the Admin panel or via API. This includes:

• Basic profile fields (name, phone, email, card number, gender, dates, tier)

• Custom attributes: PUT /api/{storeCode}/member/{member}

• Address and company details

• Agreements

CustomerRequestedSendActivationCode

Sent when a member requests an activation code:

• Send code: POST /api/{storeCode}/member/{member}/send-code

• Resend code: POST /api/{storeCode}/member/resend-code

CustomerRequestedPasswordReset

Sent when an active member requests a password reset:

• Request reset: POST /api/{storeCode}/member/password/reset/request

CustomerPhoneNumberWasChanged

Sent when a logged-in member updates their phone number in their profile.

CustomerLevelChanged

Sent when a member’s tier changes:

• Manual tier change (upgrade or downgrade)

• Tier threshold is reached

• A new member is created and the default tier is assigned

LevelWillExpire

Sent X days before tier recalculation. The value of X comes from Expiring Notifications.

CustomerEmailWasChanged

Sent when a logged-in member updates their email in their profile.

CustomerDeactivated

Sent when a member is deactivated:

• In the Admin panel

• Via API: POST /api/{storeCode}/member/{member}/deactivate