How to complete the challenge POST /api/challenger (existing X-CHALLENGER)

By Alan Richardson · Published 2026-07-31

This persistence challenge restores a saved challenger by sending a POST request to /api/challenger with the existing challenger GUID in the X-CHALLENGER header.

It differs from creating a new challenger because the request includes an existing X-CHALLENGER value and expects the server to restore that challenger rather than create a new one.

Try it now

POST /api/challenger with X-CHALLENGER to resume the current challenger

Lessons Learned

• POST /api/challenger with an existing X-CHALLENGER restores that session instead of creating a fresh one.
• 200 OK signals reuse or restoration, contrasting with 201 Created for new sessions.
• Session bootstrap endpoints can be sensitive to whether a header is present.

Suggested Experiments

• Call POST /api/challenger with no X-CHALLENGER, then with an existing one, and compare status plus headers.
• Try an unknown X-CHALLENGER value and see whether the API restores, creates, or rejects it.

Experiment with this endpoint