fetchRedemptionBatchStatus()
Purpose
Provides an aggregated list of redemption batches across all games and draws.
Used by internal operations, finance, and fulfillment teams to monitor prize distribution activity.
Endpoint
GET /api/admin/fetch-redemption-batches
Authorization
- Required Scope:
admin.readorops.audit - Token: Admin or system bearer token
Parameters
No query parameters required.
Response: Success (200 OK)
[
{
"batch_id": "batch-045",
"draw_date": "2025-06-25",
"game": "powerball",
"total_prize": 82500.00,
"slips_redeemed": 109,
"slips_pending": 6,
"status": "processing"
},
{
"batch_id": "batch-044",
"draw_date": "2025-06-23",
"game": "mega_millions",
"total_prize": 44700.00,
"slips_redeemed": 98,
"slips_pending": 0,
"status": "redeemed"
}
]
Status Values
| Value | Meaning |
|---|---|
| queued | Created but not yet routed to payout |
| processing | Actively being paid out |
| redeemed | Fully processed and completed |
Error States
| HTTP Code | Error Key | Description |
|---|---|---|
| 401 | unauthorized |
Invalid or missing admin credentials |
Integration Notes
- This endpoint is used by the admin UI to populate dashboards and audit tables.
- Batch IDs may link back to individual claim views via the batch ledger.
- Status transitions are written in real-time and audit-logged.
- Use batch-level totals to reconcile nightly payment exports.
Operational Uses
- Flag slow-moving batches
- Confirm payout completion before prize ledger locks
- Provide real-time insights during draw windows