November 2025 Release

Production Release Date: November 19

Rest APIs

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

• GET /locales - Updated to return locales in alphabetical order.

Product Updates

Users View Filters and Log Action BETA Release

The Users View Actions tab has been redesigned to hide the Event ID, combine the action time and create time into one column, include a filter by action name, and provide a method for logging a user action.

The redesign provides more space for metadata, allowing more results to be returned on each page. The new filter helps you quickly find a specific action, reducing the need to scroll through multiple pages when troubleshooting a user's activity. General release will include the ability to filter by action date.

The Log Action feature allows you to manually log an action for a user. This can be useful for testing, or to make progress on or complete a mission for a specific user. General release will include the ability to backdate the action.

Contact Nitro Support if you're interested in beta testing the new features.

Nitro Studio Access

When adding new Studio users (admin users), you now have the option to:

• Add a new user - Requires a unique email address that has not previously been used for an admin or program user.

• Promote an existing program user - Gives an existing program user administrator rights to access Nitro Studio.

• Grant access to a pre-existing user - Re-enables access to an admin user that was added and then removed. The user is added with their existing password which can be changed using the Forgot your password? link on the login screen.

**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