How to complete the challenge GET /api/challenger/guid (200)
This challenge applies when challenger persistence is enabled. Use the saved challenger GUID in the URL so the server can restore that challenger's progress from persistence into memory.
The request path is /api/challenger/{guid}. Replace {guid} with the saved challenger id.
For active sessions, the same endpoint also returns challenger progress data. For this persistence challenge, the important behaviour is that the challenger id can be restored and the response status is 200.
Try it now
GET /api/challenger/{guid} to get challenger progress
Lessons Learned
GET /api/challenger/{guid}can restore a saved challenger into memory when persistence has it available.- This route makes a
GETdo more than a normal safe read, so it is worth noting the API-specific behavior. - Restored sessions should bring back challenge progress, not just the identifier.
Suggested Experiments
- Save progress, restart or clear memory if possible, then use
GET /api/challenger/{guid}to observe restoration. - Request a made-up challenger guid and compare the error with a real saved guid.