Scalar properties will always be included in a response, unless otherwise specified.
A globally unique identifier for the huggg in GUID format.
A globally unique user identifier for the sender of the huggg in GUID format.
A globally unique user identifier for the recipient of the huggg in GUID format.
This is a different expression of this property than is to be expected elsewhere
A string representing when the huggg was sent relative to today.
A time stamp represented when the huggg was last updated. Note: The definition of "updated" is quite broad.
A globally unique identifier for the Product this huggg is for.
0 (Downloaded) or
An integer value representing the current status of the huggg. We are largely moving away from relying on this integer status flag in favour of individual flags and data-based checks. (For instance, redeemed hugggs are one's with a redemption. Expired hugggs are ones with an expiry in the past.)
5 are used consistently. However, a better check
5 (sent) would simply be, is there a receiver ID attached?
This list is non-binding and should be considered legacy
6: SMS Reminder sent
7: SMS 7 days Reminder sent
8: Unclaimed or SMS 12 days Reminder sent
9: SMS 23 Days Reminder sent
10: SMS 11 Month Reminder sent
Key Name code
If supplied this is a voucher code used to redeem the huggg. The presence of this code will depend on both the type of huggg and the stage in the hugggs lifecycle. For example cinema hugggs which require a code specific to location / segment will not present a code until the voucher has been activated, whereas EagleEye hugggs may present from purchase.
If supplied this should typically be made available to the user as a QR code.
Key Name expiry_date
The date on which this huggg expires.
Key Name shortcode