LoginSign Up
← Back to all sparks
O

Optimove

MKT AUTO
Velocity5.0

Customer-led marketing platform for orchestrating personalized multichannel campaigns.

www.optimove.com ↗

Optimove is publishing its gamification and messaging stack as APIs — and letting an AI client build the games.

marketing-automationgamificationmcpapi-surfaceschema-versioningpreference-management
◆Current state
Optimove's developer changelog is API surface work, and the pace is steady rather than dramatic. The Gamify API gains an endpoint capping how many times a player can play a campaign. The Preference Center API adds smart-campaign preference endpoints for topics hidden from the UI. Data Share now documents three schema generations side by side with version tabs so customers migrate on their own schedule. Around them sits documentation correction work — parameter types, response behaviour, error handling on the conditional execution endpoints.
◆Where it's heading
Two things are happening at once. The platform is being exposed programmatically across every module — gamification, preferences, SMS, overlay messaging, conditional execution — which shifts Optimove from a campaign UI toward something other systems drive. And the AI Minigame Creator, which generates and publishes playable minigames from natural language through the Optimove MCP, points at where that leads: the API surface exists partly so an AI client can operate it. Side-by-side schema versioning suggests a customer base large enough that forced migrations are not an option.
◆Prediction
Given the Gamify API is accumulating operational controls alongside the MCP-driven creation path, expect more guardrail endpoints — limits, eligibility, spend — since generated campaigns need bounds. The volume of documentation corrections suggests the API reference is still catching up to the implementation.

◆Recent moves

  1. 4d ago

    Gamify API: Set Player Gameplay Limit

    A Gamify API endpoint for capping how many times an individual player can play a campaign. Read against the MCP-driven minigame creation shipped a month earlier, this is the guardrail half — generated games need enforceable limits before anyone runs them against real customers.

    View source ↗
  2. 24d ago

    Preference Center API: Smart Campaign Preferences endpoints + preference endpoint updates

    New GET and PUT endpoints for smart-campaign subscription preferences, covering topics configured as hidden from the UI. Extends preference management to categories customers cannot see, which is the case that previously had no programmatic path.

    View source ↗
  3. 28d ago

    Data Share: V1.5 and V1.6 schema versions now available

    Data Share documents V1.3, V1.5 and V1.6 side by side with version tabs on each dataset page and a version selector on the entity relation diagram, with V1.3 remaining fully available. Publishing three live schema generations at once is what a vendor does when customers cannot be moved on the vendor's timetable.

    View source ↗
  4. 29d ago

    Conditional Execution endpoints — clearer parameters, responses, and error handling

    Expanded documentation for the two Scheduled Conditional Execution endpoints, making request and response behaviour explicit to reduce integration errors. Documentation only — no change to the endpoints themselves.

    View source ↗
  5. 1mo ago

    API Reference corrections: request body parameter types

    Two request body parameter types corrected in the API reference where the documented type could cause failed requests. A reference fix, though it points at documentation trailing the implementation.

    View source ↗
  6. 1mo ago

    Customer Execution Details By Campaign — customer attribute parameters documented

    Two previously undocumented optional query parameters on the Customer Execution Details By Campaign endpoint are now described, covering how to request customer attribute values and set the delimiter. Existing behaviour written down rather than new behaviour added.

    View source ↗