get_reward_status

get_reward_status nodes inspect a reward pool before a user spins or scratches.

Summary

• Placement: Mid-flow.
• Context: Client apps and backend apps.
• Visual: No.
• Level: Easy.
• Purpose: Check availability before showing reward interactions so users see accurate stock messaging.

• Returns remaining counts, per-user attempt limits, and cooldown data.
• Writes results to a configurable $state path so UIs can disable CTA buttons when stock is empty.
• Provides on_error routing to handle pool outages or API errors without blocking the campaign.