June 2026 Release **Beta**

Production Release Date: June 24 - Planned

The following features, planned for the upcoming June release, are currently available in Sandbox for Beta testing. Our Production release could differ from the information detailed here.

Discontinuation Notice

Legacy OAuth Tokens with Blocks

Legacy OAuth tokens used with blocks have now been deprecated. When embedding an Impact or Recognitions block, you must use a JWT token (Gamification Web Token) from the /gamification-token API.

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

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

Go View

The Go view in Nitro Studio has been removed from the platform. This view was used to configure the content and imagery in a Bunchball Go program. If you need to update an existing Bunchball Go program, contact your account team for assistance.

Rest APIs

The following API change is documented on https://api.sandbox.bunchball.com/docs.

• POST /gamification-token - Updated to include the upsertUser parameter. When you request a gamification token for a user that doesn't already exist in Nitro and upsertUser is set to:

  • true - the user is automatically created.

  • false - the request returns a 404 error.

Product Updates

Gamification Token Requests

Now, when you request a gamification token for a user that doesn't already exist in Nitro, the user is automatically created. To prevent automatic user creation:

1. Pass upsertUser=false in your token request.

2. The request will return a 404 error if the user doesn't exist instead of generating a token and creating the user.

3. When you get a 404 error, call PUT /users/{userId} to add the user to Nitro and enroll them in groups, the award account, etc.

4. Retry the gamification token request once the user has been created.

Award Account Transaction Descriptions

Descriptions on award account transactions have been updated to only display the mission name, recognition category, tags added to a manual debit/credit, or the description provided in a points import. Previously, the transaction was prefaced with the type (for example, challenge:<mission name>).

In Nitro Studio, the Users view Balances tab will continue to show the full transaction details. You will see the shortened description in:

• a points webhook

• Cashier bank transactions

• the Impact award account statement

Current	Previous

Product Fixes

• Fixed an issue in the Action detail view where the "Used in Missions" link was not opening the mission.

• Fixed an issue in data import where filtering on some import types returned an error.

• Fixed an issue in Impact where an error displayed when closing the detail view after accessing the mission directly from an external link.

• Fixed an issue in Impact+ where logging out displayed a "logging out" message before returning to the login page. This delay has been removed and logging out returns you immediately to the login page.

See also

Release Notes