This webhook is sent each time an individual reward is successfully issued
to a user during a partner issuance job. If a batch contains 100 identifiers,
up to 100 individual reward.issued webhooks may be sent (one per
successful issuance).
Event
reward.issued
Payload Description
string
The event type: reward.issued
string
The time the event occurred (ISO8601)
hash
Event data
Show data
string
The ID of the issuance job that triggered this reward
string
The ID of the merchant associated with the issuance job
string
The ID of the issued reward
hash
The identifier used to issue the reward
Show identifier
string
Identifier type: email or phone
integer
Position in the original identifiers array
string
The ID of the user who received the reward, if found
string
The state of the reward. The value is available, active, used, or
pending. The value is never null or an empty string ("").
string
The date the reward stops being redeemable (ISO8601), or null when the
campaign sets neither a redemption end date nor a relative window.When both are set, this is whichever comes first: the campaign’s
redeemable_to, or retire_after_days counted from the moment the reward
was issued. It is the same date the guest sees and the one redemption
enforces.
hash
Campaign information
Show campaign
string
Campaign ID
string
Campaign name
string
Campaign objective
string
Campaign start date (ISO8601)
string
Campaign end date (ISO8601)
string
Reward redemption start date (ISO8601)
string
Reward redemption end date (ISO8601)
string
Campaign time zone
string
Terms and conditions
hash
The variant used for issuance
Show variant
string
Variant ID
string
Variant name
string
Reward template ID
On an evergreen campaign — retire_after_days set and no redeemable_to —
expires_at is the only field in this payload carrying the reward’s expiry
date. campaign.redeemable_to is null by design.