Skip to main content

Overview

Use this page as the behavior hub for gamification runtime semantics. Detailed behavior docs:
  • Quests: /repositories/d-sports-api/gamification/quests
  • Points: /repositories/d-sports-api/gamification/points
  • Leaderboards: /repositories/d-sports-api/gamification/leaderboards
  • Rewards: /repositories/d-sports-api/gamification/rewards
  • Achievements: /repositories/d-sports-api/gamification/achievements

Behavior focus areas

  • Progress checks and completion gates
  • Daily quiz sessions under /api/v1/engage/quests/*
  • Points write/read consistency
  • Leaderboard season-scoped ranking outcomes
  • Reward claim/redeem decision paths
  • Fan Rep is a separate ledger — see Fan Rep

End-to-end quest lifecycle

  1. Fetch active quests and eligibility context.
  2. Start/advance quest progression through quest routes.
  3. Resolve completion and points side effects.
  4. Refresh rewards and leaderboard views after mutation events.

Pass transition scenarios

  • User gains or loses global pass eligibility.
  • User enters/exits event pass eligibility windows.
  • Quest availability and completion pathways shift based on pass state.

Cross-team user progression behavior

  • Team-scoped quest progression can vary across user team contexts.
  • Team/favorites updates can change available quest surfaces.
  • Server responses remain source-of-truth for progression state.