October 2026 Release
Production Release Date: October 28
Rest APIs
The following API changes are documented on https://api.bunchball.com/docs.
-
PUT /challenges/{challengeId} - Updated to allow changes to 1 or more attributes (less than all) and only those attributes are updated. Previously, any attributes that were not updated in the request would reset to their default values.
-
/challenges - Updated to include the fullLabels array that returns all labels associated with the mission and the attributes for tenure window.
-
windowOpensInRelativeDays - Any positive or negative number that determines when the mission opens relative to the user's tenure date.
-
windowDurationDays - Any positive number, or -1 for unlimited, that determines how long the user remains eligible after the mission opens.
-
Product Updates
** Upcoming Webhook Mission Reversals **
In our November 2026 release, we'll be updating our mission completion webhook to include mission reversal events. A new completionStatus parameter will be added indicating if the mission event occurred because the mission was completed or removed. See Webhooks for an example of a mission completion events post call.
If your program uses mission completion webhooks, ensure you prepare for this change to ensure accurate data reporting.
Tenure Date BETA Release
A new reserved preference, tenureDate, is now available to track a user's tenure date and dynamically determine mission eligibility based on tenure milestones.
-
Add a user's tenure date via data import, APIs, or the Preferences tab in the Users view.
-
Create missions that dynamically determine eligibility based on a user's tenure date.
-
During the Beta release, you must create or update a mission via API to use tenure date. Tenure date configuration will be available in the mission builder for General Release.
API Configuration Options
-
windowOpensInRelativeDays - Specifies when a mission becomes available relative to the user's tenure date.
-
windowDurationDays - Specifies how long the user remains eligible after the mission opens. The duration is inclusive of the open date.
Examples
|
Mission Configuration |
User and Tenure |
Eligibility |
|---|---|---|
|
Meet with your manager mission
|
User A's tenure date = April 10, 2026 |
Mission opens for user A on April 10th and closes on April 19th. |
|
User B's tenure date = April 20, 2026 |
Mission opens for user B on April 20th and closes on April 29th. |
|
|
Complete your certification mission
|
User C's tenure date = March 1, 2026 |
Mission opens for user C on February 24th and closes on March 20th. |
|
User D's tenure date = March 15, 2026 |
Mission opens for user D on March 10th and closes on April 3rd. |
Repeatable Window Missions BETA Release
You can now create repeatable window missions that automatically open and close on a recurring schedule. A repeatable window mission can be configured to repeat daily, weekly, monthly, or quarterly, with an availability window, such as "open every Friday at 8:00am and close at 5:00pm".
Repeatable window missions use the same prerequisites, rules, and rewards as one-time or unlimited repeatable missions.
With repeatable window missions you can:
-
Create a recurring schedule that repeats daily, weekly, monthly, or quarterly.
-
Define the date and time the recurring window opens and closes.
-
Limit how many times a user can complete the mission within each window (for example, up to 2 completions per month).
-
Set an overall completion limit across all windows (for example, a total of 10 completions before the user becomes ineligible for the mission).
Beta Limitations
During the Beta cycle, historical completion data is not stored for repeatable windows. As a result, reward adjustments are applied based on the mission's current configuration. For example, if a participant earns 10 XP from a mission and the reward is later changed to 5 XP, removing that completion will deduct 5 XP rather than the original 10 XP. Additionally, support for adding or removing completions within a specific window is still in development.
If you're interested in beta testing repeatable window missions, contact Nitro Support.
Award Account Negative Bank Balances
Nitro now supports negative award account balances when necessary. Previously, transactions sent from Nitro to the bank could not reduce an award account balance below zero. This could cause issues when points had already been earned and spent, but later needed to be debited or reversed.
With this update, Nitro can process debit transactions that result in a negative balance, ensuring point adjustments and reversals are accurately reflected in the award account balance.
Impact Award Account Browse and Unverified
When a program requires a user to be verified for the award account catalog, an unverified user will now see a Browse button instead of Redeem and an informational message indicating they are unverified. If no browse-only link is set for the catalog, only the unverified message displays.
Impact On The Spot Claim Button
The OTS Claim button in Impact now respects a user's verification status. If your program is set to verify a user for point rewards and the user is unverified, the Claim button will be hidden. If an unverified user cannot earn points from missions, they also can't earn from an OTS card.
Repeatable Missions Filter
The Nitro Studio Missions list view filter has been updated to include all repeatable mission types. You can now filter the missions list by not repeatable, repeatable unlimited, and repeatable window missions.
Studio User Password Fields
Password fields have been removed from the New Studio User setup. When adding a Studio user (admin user), you do not need to set their password. The user adds a password when they log in for the first time and sign up for an account.
Product Fixes
-
Fixed an issue where the block builder was not correctly setting the leaderboard return count when creating a new block.
See also