Platform age signals documentation
We've published end-to-end documentation for platform age signals: how Apple iOS, Google Play, Xbox, Meta Horizon, and k-ID age data flows into k-ID, when the age gate can be skipped, and how verified versus unverified signals interact with high-risk permissions and age assurance.
What's New
CDK — Platform age signals
- Platform age signals — Quick integration paths, API map, recommended request sequence, how
POST /age-gate/checkuses a platform signal, supported platforms and verified declaration types, and verified versus unverified signal behavior. - Platform signal details — Per-platform field shapes, how to obtain each native signal, endpoint-by-endpoint notes (
get-requirements,check,get-default-permissions,session/get,get-platform-age-range,session/upgrade), validation, age conflicts, andk-idsignal rules.
Concepts and related documentation
- Age signals — How platform age signals fit alongside other signal types and where to go for
PlatformAgeSignalintegration details. - Age assurance for high-risk features and Permissions — Cross-linked behavior for
verifiedAgeThresholdand verified platform signals at the age gate.
API reference (OpenAPI)
Descriptions for session upgrade, AgeVerification, and platformAgeSignal now use verified platform signal wording consistently with the docs above.