API Events

Incoming Events (Operator to Game)

The OperatorInterface sends these events to the game. Listen to them with OperatorInterface.on().

Game Control

• spinRequested: Operator requests a spin.
• spinStopRequested: Operator requests to stop the spin.
• stopRequested: Operator requests to stop the game.
• stopAutoplayRequested: Operator requests to stop autoplay.
• pauseRequested: Operator requests to pause the game.
• resumeRequested: Operator requests to resume the game.
• reloadRequested: Operator requests to reload the game.

Settings

• muteRequested: Operator requests to mute the game.
• unmuteRequested: Operator requests to unmute the game.
• toggleMuteRequested: Operator requests to toggle mute.
• enableTurboRequested: Operator requests to enable turbo mode.
• disableTurboRequested: Operator requests to disable turbo mode.
• toggleTurboRequested: Operator requests to toggle turbo mode.

Stake Control

• increaseStakeRequested: Operator requests to increase stake.
• decreaseStakeRequested: Operator requests to decrease stake.
• updateStakeRequested: Operator requests to update stake.

UI

• showRulesDialogRequested: Operator requests to show rules.
• hideRulesDialogRequested: Operator requests to hide rules.
• showAutoplayDialogRequested: Operator requests to show autoplay dialog.
• showErrorDialogRequested: Operator requests to show error dialog.

Other

• clearCookiesRequested
• continueRequested
• updateBalanceRequested
• handleFreeRoundsUpdate
• setPromoInfoResponse
• getPromoInfoResponse

Operator Messages (Operator to OperatorInterface)

These are the raw postMessage types that an operator wrapper sends to the game window (the OperatorToOperatorInterfaceMessage type). The OperatorInterface's generic message handler maps each type to the corresponding incoming event listed above. The handler then forwards the event to the game. See Appendix A: Events for the postMessage format.

For most operators, the OperatorInterface reads the message string from e.data.type. For EveryMatrix, it reads the message string from e.data.name. For Lottoland, it reads the message string from e.data.action. For Playtech POP, it reads the message string from _type. The OperatorInterface reads the payload from e.data.data.

Message	Forwarded to the game as
spin (also spinRequested, requestSpin)	spinRequested
stop (also stopRequested)	stopRequested
spinStop (also spinStopRequested)	spinStopRequested
clearCookies	clearCookiesRequested
stopAutospins / stopAutobet	stopAutoplayRequested
stakeUp	increaseStakeRequested
stakeDown	decreaseStakeRequested
turbo	no data → toggleTurboRequested; true → enableTurboRequested; false → disableTurboRequested
toggleMute	no data → toggleMuteRequested; true → muteRequested; false → unmuteRequested
setAudio	true → muteRequested; false → unmuteRequested (no data is ignored)
updateBalance	updateBalanceRequested
showHelp (also paytableshow, showPaytable)	showRulesDialogRequested

Not routed by the generic handler

The OperatorToOperatorInterfaceMessage type also declares reload, pause, resume, mute, unmute, and stopAutoplay. The generic postMessage handler does not map these strings. Operator-specific SDK callbacks emit the corresponding *Requested events instead. For example, Relax Gaming's feim callback maps freeze → pauseRequested, unfreeze → resumeRequested, pauseAutoPlay → stopAutoplayRequested, and updateSettings → muteRequested/unmuteRequested/enableTurboRequested/disableTurboRequested. Playtech POP's UCIP pause command also emits its event this way. The package declares reloadRequested. The package never emits it.

For messages that the game sends to the operator, see the notification methods (for example gameReady, roundStarted, balanceUpdated) in the API Methods reference.