Two new endpoints in the Loyalty System API. Level rewards are no longer granted automatically; players claim them through a new endpoint, surfaced by a new claimableLevels field on the player level response. Calculated-reward missions, which issue dynamic reward amounts per qualifying event using a formula, now have their own listing endpoint.
Updated Registration Initiated and Registration Failed event references
The Registration Initiated and Registration Failed event reference articles have been updated to align with the latest event definitions — covering the event key, parameters table, and JSON example for both events.
Impact: Implementations sending Registration events should verify their payloads match the updated schema.
Self-Exclusion: Lifted — fired when a self-exclusion period ends and the customer is reinstated
Impact: Implementations that need to track responsible gambling workflows should integrate these events. Review the event schemas and align your payloads accordingly.
Customer Data API
Upsert Customer endpoint marked as legacy — use Batch Add Customers
The Upsert Customer (PUT /customers/upsertcustomer) endpoint has been marked as a legacy API. The article now directs developers to the Insert or Update Customers endpoint, which supports batch operations and is the recommended approach for all new implementations.
Impact: No breaking change — the legacy endpoint remains functional. New integrations should use the batch endpoint.
Impact: Documentation only — no changes to data schema required.
SDK & Integration
Updated Flutter SDK version to 3.3.3
The optimove_sdk_flutter dependency version referenced in the Optimobile Getting Started integration guide has been updated from an outdated version to the current release:
dependencies:
optimove_sdk_flutter: 3.3.3
Impact: Developers setting up a new Flutter integration should use version 3.3.3. Existing integrations should check their pubspec.yaml against the latest release.
Renamed "Track & Trigger" to "real-time" throughout Web SDK Integration guide
All references to "Track & Trigger" and the abbreviation "T&T" in the Web SDK Integration guide and its child articles have been updated to use current terminology — "real-time" or "real-time capabilities" depending on context.
Impact: Documentation only — no functional changes.
Data Sharing
Fixed broken Snowflake links in Data Sharing Methods
Three broken links pointing to the Snowflake documentation in the Data Sharing Methods article have been fixed. The affected links were: Reader Accounts Overview, Snowflake Data Sharing Concepts, and Snowflake Credit System Concepts.
Impact: Documentation only — no functional changes.
OptiPromo
Updated Promo System Safeguards and Best Practices article
The article title has been updated to "Promo System Safeguards and Best Practices".
A sentence in the Manual Promo Backup section has been corrected: "campaign execution" has been changed to "promotion allocation", and "system" has been changed to "Optimove".
Impact: Documentation only — no functional changes.
The Loyalty System API is now live in the Developer Hub. Build custom widget frontends for your loyalty program with 20 endpoints covering brands, players, missions, rewards, badges, and leaderboards.
In a scenario where the parameter BrandId is not associated with channel Optimail, the response will be 404. If you experienced this error, please revisit the BrandId parameter you are using.
