March 2026 Release

Production Release Date: March 25

Rest APIs

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

• GET /groups - Updated to include the noClasses parameter. When true, only groups not associated with a group class are returned. Defaults to false which returns all groups.

• GET /exchanges - Updated to include the ids parameter. Accepts a comma-separated string of exchange Ids.

• The following APIs have been deprecated. They will be remain on the platform until an end of life date has been communicated.

  • GET /events

  • GET and POST /users/{userId}/interactions - Replace with /users/{userId}/interactions-collection.

Product Updates

Impact Leaderboards

Leaderboards in Impact have been updated to:

• show a loading state when switching between available leaderboards.

• show a wider leaderboard selector to fit leaderboard names. Some names may still truncate if they exceed the maximum width.

Swagger Authentication

When you access our RESTFulAPI site (Swagger) via Nitro Studio, you are automatically authenticated and don't need to authorize with a token.

Use the API Documentation link to allow Nitro to authenticate your session. Ensure you log out of the session when you leave the API site.

Product Fixes

• Fixed an issue where point categories configured with an initial credit amount were resetting a user's balance at 0 instead of only when a new user was added.

Discontinuation Notices

Push Subscriptions

Effective with the April 2026 release, Bunchball Go push notifications will be deprecated and removed from the platform. Push notifications were used to deliver in-browser alerts when a user received a recognition. Starting with our April 2026 release, users will no longer be able to opt in to push notifications and will stop receiving recognition alerts, even if they were previously subscribed.

Bunchball Go was deprecated in June 2025 and replaced with Impact+, which provides a more modern, integrated solution.

Legacy OAuth Tokens

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