Adaptive Access overview
The CDK reference for Adaptive Access: product-level and feature-level age assurance, from Compliance Studio settings to the unlocked session.
Adaptive Access is how CDK runs age assurance. k-ID decides when a user must prove their age, runs the check, and saves the result on the user's session, so your app reads the outcome from permissions instead of handling verification results itself.
One flow, two entry points
Every Adaptive Access check follows the same path:
- Settings. You choose in Compliance Studio whether to check at entry, at features, or both, and you can change that per market. See Configure Adaptive Access.
- The API response. At entry,
POST /age-gate/checkreturns aCHALLENGE_AGE_GATE_AGE_ASSURANCEchallenge. At a feature,POST /session/upgradereturns aCHALLENGE_SESSION_UPGRADE_BY_AGE_ASSURANCEchallenge. - The check. You present
challenge.url, and the user verifies with one of your product's methods. - The result. You confirm the outcome server-side with the
Challenge.StateChangewebhook or/challenge/get-status. A redirect back to your app isn't the result. - The session. You read the session with
/session/getand turn features on from each permission'senabledvalue.
One integration isn't one request. Product-level and feature-level checks use different endpoints and challenge types, so handle each one where it happens.
Reference pages
Proof of age at the age gate. The session is created after the user passes.
Feature-level age assuranceProof of age when the user reaches a protected feature, through /session/upgrade.
Methods, facial age estimation margins, and what the session records.