Rewards overview

Understand how rewards let Loyalty v2 members redeem their points for material products or digital incentives

A reward is what a member actively redeems by spending points, unlike a benefit, which is granted automatically by an earning rule. Rewards are optional and only become redeemable once assigned to a program with a stock configuration.

Reward types

A reward requires name, type, and costs, plus exactly one type-specific object matching its type:

• MATERIAL: A physical product or SKU, defined in the material object.
• DIGITAL: A discount coupon or gift card, defined in the digital object.

Costs and program assignment

A reward’s costs array can define a different point price per card definition, so the same reward can be connected to multiple point wallets – even across different programs – each with its own price. The reward itself doesn’t carry stock; stock is set per program when the reward is assigned through the Programs batch assignment endpoint, and can be updated afterwards without going through the batch flow again.

Validity and refunds

A reward can define validity_hours to restrict when it’s redeemable (defaulting to any time), and refunds behavior for what happens to spent points when a reward purchase is refunded.

Lifecycle

A reward can be created directly in DRAFT or ACTIVE status. From there, it follows the same three-state pattern as earning rules and tier structures: DRAFT/INACTIVE > ACTIVE with the reward activate endpoint, ACTIVE > INACTIVE with the reward deactivate endpoint, and ACTIVE > DRAFT with the reward draft endpoint for unassigned rewards. While in DRAFT, every property can be updated; once active or inactive, only name, metadata, refunds, validity_hours, start_date, end_date, and costs can still change. Deleting a reward moves it to a DELETED status.

Redeeming and checking availability

Members redeem rewards through the member reward-purchase endpoint, which spend points from the card tied to the reward’s cost configuration and can later be refunded. Before building a redemption flow, use the Examine overview endpoint to check which rewards a member can currently afford and why any others are unavailable.

Related resources

• Loyalty v2 API: Overview for the full Loyalty v2 API map.
• Programs overview for assigning rewards and their stock to a program.
• Members overview for purchasing and refunding rewards.
• Benefits overview for the automatically granted counterpart to rewards.
• Create loyalty rewards for the dashboard perspective on configuring rewards.