January 2026 Release

Production Release Date: January 28

Rest APIs

The following API changes are documented on https://api.bunchball.com/docs.

• PUT /users/{userId} and /group-classes APIs - Updated to include two new parameters:

  • autoCreateGroups - Allows or restricts the automatic creation of groups within the group class. Returns true/false.

  • description - The group class description.

Product Updates

Hidden Missions

We've added new options for hidden missions that determine if the mission shows in the missions list and trophy case. You can choose to:

• Hide a mission until the user completes it.

• Hide a mission until it's unlocked and the user is eligible to complete it.

• Always hide a mission.

Hidden options are now set on the mission builder Availability tab.

Nitro Studio and Recognitions Search

Search functionality in the Nitro Studio Users view and Recognitions block has been enhanced to include the user's additionalName preference. In large programs, this preference can be used to store the user's location, email, or some other unique identifier you want to be searchable.

This is a forward-facing update, so affected users need to be updated to appear in search results. Adding or editing the additionalName user preference for existing users will trigger an update.

Mission Recommendation Engine

The mission recommendation engine has been updated based on learned patterns, user behaviors, and program needs. The mission recommender now gives more weight to mission importance. Assigning a mission very high, high, low, or very low importance will help determine where the mission falls in the mission order. The mission recommendation engine leverages importance and other gamification principles to provide users with relevant and engaging content personalized for their path to success.

Group Class Description and Automatic Group Creation

We’ve introduced the ability to add a description to group classes, making it easier to understand and identify the groups within the group class.

You can also allow the automatic creation of groups within a group class. When this option is selected and you enroll users in a group via API (PUT /users/{userId}) or data import, a group will be created within the group class if that group doesn't already exist.

When enabling this option, ensure your user import contains accurate data. Inaccurate group information (incorrect or misspelled group names) will result in users being enrolled in "bad" groups with no reported errors.

Data Import Group Enrollment

The group enrollment file in data import has been updated to support a maximum of 15 group classes. Group enrollment allows you to add users to groups and create new groups and group classes if they don't already exist.

Site Settings Redesign

The Site Settings view has been redesigned for a more modern look. The new view consolidates information onto two tabs and adds the ability to copy your API keys with a copy button that appears on hover. Some legacy features, such as Session Timeout and Userlink URL have been deprecated and removed from the platform.

Product Fixes

• Fixed an issue when granting Nitro Studio access to a pre-existing user where the password was not cleared before the user was added.

**Legacy OAuth Token Discontinuation Notice**

Effective with the June 2026 release, legacy OAuth tokens used with blocks will be deprecated.

What this means for you?

• Impact and Recognitions blocks will require a JWT gamification token from the /gamification-token API.

• Legacy OAuth tokens will no longer be supported for blocks, and new features released in blocks may not work with the old token.

• If your program uses both blocks and web components, you must use two separate tokens:

  • A JWT gamification token for blocks

  • A legacy OAuth token for web components

To prepare for the upcoming token deprecation, you should take the following steps before June 2026.

1. Review the token used in your Impact block to ensure you’re using a JWT gamification token.

2. Review the token used in your Recognitions block to ensure you’re using a JWT gamification token.

3. Update your embed code to use a correct token if you're not using a JWT gamification token in all of your blocks. Use the steps detailed here to update.

4. Ensure you have two tokens enabled if you have both web components and blocks in the same environment:

   • A JWT gamification token for blocks

   • A legacy token for web components

Legacy OAuth tokens used in web components will continue to be supported until the official end-of-life date for web components is announced.

See also

Release Notes