CDKAdaptive Access

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:

  1. 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.
  2. The API response. At entry, POST /age-gate/check returns a CHALLENGE_AGE_GATE_AGE_ASSURANCE challenge. At a feature, POST /session/upgrade returns a CHALLENGE_SESSION_UPGRADE_BY_AGE_ASSURANCE challenge.
  3. The check. You present challenge.url, and the user verifies with one of your product's methods.
  4. The result. You confirm the outcome server-side with the Challenge.StateChange webhook or /challenge/get-status. A redirect back to your app isn't the result.
  5. The session. You read the session with /session/get and turn features on from each permission's enabled value.

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

Quick starts

On this page