Product API

KUID in Age Gate Check

We’ve added support for passing a k-ID User ID (KUID) — a unique identifier for each player — to the /age-gate/check API endpoint. Developers who have obtained prior consent for a player can now use the associated KUID to uniquely identify which player is requesting parental consent for new games. This ensures game additions apply only to the intended child account. When included in API requests, the KUID restricts child account selection during VPC flows. Valid KUIDs skip redundant child selection screens, streamlining the user experience, while unauthorised KUIDs trigger an error (“you don’t manage this kid”). This enhancement improves accuracy by preventing mismatches, reduces UI steps, and enforces strict child-account alignment.

Bugs & Enhancements

We’re always striving to make our tools better for you. In this release, you’ll find a variety of thoughtful improvements and fixes across the Family Portal, Developer Portal and Product APIs — each designed to make your experience smoother, more reliable, and easier to use:

Family Portal

• Updated the sender name of parental approval emails from “no-reply” to “k-ID” to improve email deliverability, following best practices for sender reputation management and spam filter avoidance.

• Removed parent verification requirements in the parental attestation flow when a child’s age check fails, saving parents’ time by skipping redundant verification steps for accounts that do not meet the access age criteria.

Developer Portal

• Resolved an error causing network/console errors during toggle interactions (e.g., enabling/disabling settings) on Product Access and Overrides pages.

• Fixed a bug in Custom Permissions where permission titles and descriptions exceeding character limits were displayed in full on the Developer Portal’s Review page and Family Portal’s permission management pages. Excess text is now properly truncated across all pages.

Product API

• Where a sub-jurisdiction does not have its own dedicated configuration or any overrides, it now automatically inherits the configuration of its parent jurisdiction. However, if a configuration exists for the sub-jurisdiction, those settings will override the parent jurisdiction’s configuration. Sub-jurisdiction overrides always take precedence over parent jurisdiction overrides. Examples of sub-jurisdictions include CA-BC (British Columbia, Canada), GB-SCT (Scotland, United Kingdom), and US-CA (California, United States). For a full list of our supported jurisdictions, see our Documentation.

• Resolved case-sensitivity issues with parent emails: uppercase characters in email addresses will no longer cause errors during session upgrades.