PROHIBITED status documented for age gate widget redirects
The age gate and end-to-end widgets return status=PROHIBITED when a player is below your product's minimum age. That status is now documented on the widget redirect URL, in the Widget.AgeGate.Result event, and in the API reference, so you can reliably detect and block below-minimum-age players.
What's new
CDK: Embedded flow
- Receiving the result on the redirect URL: New section covering the
redirectUrlcallback query parameters (status,sessionId,challengeId,age) for both the age gate and end-to-end widgets, with a below-minimum-age example. - The event-handling example now branches on all three statuses (
PASS,FAIL,PROHIBITED).
Event reference
Widget.AgeGate.Result: Added a status-values table (PASS/FAIL/PROHIBITED), thedata.agefield returned onPROHIBITED, and aPROHIBITEDexample.
API reference (OpenAPI)
- The
redirectUrldescriptions for/widget/generate-age-gate-urland/widget/generate-e2e-urlnow listPASS,FAIL, andPROHIBITED, and explain thatPROHIBITEDappends the enteredageand creates no session.
Treat the redirect and event status as a UX hint: confirm the outcome server-side via the Challenge.StateChange webhook or /session/get before granting access.