Features

RTP management

RTP (return to player) is the share of the stakes that the games pay back over time. The platform lets you steer it between 60 % and 100 %: for the whole project and, optionally, for each player. Use this page to understand which level a round gets and to manage player levels over the API.

How a round gets its RTP#

The level is resolved before the debit, inside the same transaction as the paid round, and then stays fixed for that round. A change applies from the next round; started rounds finish at their own level.

1. Default. A project without saved RTP settings plays at 90 % (the provider RTP). The games' natural mathematics is used only if an owner explicitly saves "no provider RTP".
2. Provider RTP set, personal RTP off. Every player's rounds are played at the project's provider RTP. Manual player levels are ignored.
3. Personal RTP on. Each player has their own level (below).

Free-spin rounds go through the same logic and count in the adaptive window with their nominal bet. Target-outcome rounds are marked and do not count in the window.

Project settings#

Set in the admin panel under RTP & players (the platform owner edits the project settings; see Admin).

Personal RTP of a player#

• A new player is bound at their first round to the provider RTP that is current at that moment (start level = current level).
• The level can be changed manually (admin panel or API, 60–100 %, up to two decimals, with a reason kept in the player's journal). A manual level freezes the adaptive rule for that player until you return them to auto.
• In auto mode the player plays at their current level, capped by the provider RTP at the time. If the provider RTP is lowered below a player's level, the player plays at the provider RTP.
• A manual level is not capped by the provider RTP.
• The journal of every player records who changed the level, when and why (binding, rule steps, manual changes).

Adaptive rule#

The rule watches the realised return of a player's last settled rounds. If a player is too lucky it lowers their level a little; when the luck ends it brings them back, but never above their starting level.

At most one step is made per window. The level never goes below 60 %. Players with a manual level are not touched.

On short samples the observed RTP can differ from the target; this is normal.

POST /playerRtp.do#

Manage a player's level and personal bet limits. Every action needs partner, api_key and an allowlisted IP. The request is not idempotency-key aware and is not rate limited. Common fields:

Every action answers {"status": "ok", "player": {…}}; the player object is described under get.

Errors that apply to every action: INVALID_ACTION (400) for an unknown action, INVALID_PLAYER (400) for a player_id outside the allowed characters, RTP_PROVIDER_UNSUPPORTED (400) for another provider.

get#

Returns a player's state for one provider.

Request#

curl -s -X POST https://notell-api.com/playerRtp.do \
  -H 'Content-Type: application/json' \
  -d '{"partner":"demo-casino","api_key":"YOUR_API_KEY","action":"get","player_id":"player-1024","provider":"pragmatic"}'

{
  "partner": "demo-casino",
  "api_key": "YOUR_API_KEY",
  "action": "get",
  "player_id": "player-1024",
  "provider": "pragmatic"
}

The common fields above are the only ones.

Response#

{
  "status": "ok",
  "player": {
    "partner": "demo-casino",
    "player": "player-1024",
    "nickname": null,
    "bound": true,
    "provider": "pragmatic",
    "startBps": 9000,
    "currentBps": 8800,
    "mode": "auto",
    "roundsSinceAdjust": 120,
    "providerBps": 9000,
    "effective": {"bps": 8800, "source": "player"},
    "betLimits": [{"currency": "EUR", "minMinor": "10", "maxMinor": "5000"}],
    "journal": [
      {
        "provider": "pragmatic",
        "actor": "bind",
        "reason": "bound before the first round by a level change",
        "fromBps": null,
        "toBps": 9000,
        "fromMode": null,
        "toMode": "auto",
        "windowRounds": null,
        "windowRtpPpm": null,
        "at": "2027-02-15T10:00:00.000Z"
      }
    ],
    "providers": [
      {"provider": "pragmatic", "startBps": 9000, "currentBps": 8800, "mode": "auto", "roundsSinceAdjust": 120, "effective": {"bps": 8800, "source": "player"}, "updatedAt": "2027-02-15T10:00:00.000Z"}
    ]
  }
}

Errors#

set#

Sets a manual level (mode manual). The player is bound to the provider on first use.

Request#

curl -s -X POST https://notell-api.com/playerRtp.do \
  -H 'Content-Type: application/json' \
  -d '{"partner":"demo-casino","api_key":"YOUR_API_KEY","action":"set","player_id":"player-1024","provider":"pragmatic","rtp":94.5,"reason":"VIP agreement"}'

{
  "partner": "demo-casino",
  "api_key": "YOUR_API_KEY",
  "action": "set",
  "player_id": "player-1024",
  "provider": "pragmatic",
  "rtp": 94.5,
  "reason": "VIP agreement"
}

Response#

{"status": "ok", "player": {…}} with mode: "manual", currentBps: 9450 and effective.source: "manual". The object is described under get.

{
  "status": "ok",
  "player": {
    "partner": "demo-casino",
    "player": "player-1024",
    "nickname": null,
    "bound": true,
    "provider": "pragmatic",
    "startBps": 9000,
    "currentBps": 9450,
    "mode": "manual",
    "roundsSinceAdjust": 0,
    "providerBps": 9000,
    "effective": {"bps": 9450, "source": "manual"},
    "betLimits": [],
    "journal": [],
    "providers": []
  }
}

(journal and providers are shortened here; the real answer lists them.)

Errors#

auto#

Returns the player to automatic mode: the adaptive rule resumes from the current level. The player is bound to the provider on first use.

Request#

curl -s -X POST https://notell-api.com/playerRtp.do \
  -H 'Content-Type: application/json' \
  -d '{"partner":"demo-casino","api_key":"YOUR_API_KEY","action":"auto","player_id":"player-1024","provider":"pragmatic","reason":"VIP period over"}'

{
  "partner": "demo-casino",
  "api_key": "YOUR_API_KEY",
  "action": "auto",
  "player_id": "player-1024",
  "provider": "pragmatic",
  "reason": "VIP period over"
}

Response#

{"status": "ok", "player": {…}} with mode: "auto". The object is described under get.

Errors#

bet-limit#

Sets or removes a player's own bet limit for one currency. The limit applies together with the project limits; the smallest maximum wins (Bet limits).

Request#

curl -s -X POST https://notell-api.com/playerRtp.do \
  -H 'Content-Type: application/json' \
  -d '{"partner":"demo-casino","api_key":"YOUR_API_KEY","action":"bet-limit","player_id":"player-1024","provider":"pragmatic","currency":"EUR","min_minor":"10","max_minor":"5000"}'

{
  "partner": "demo-casino",
  "api_key": "YOUR_API_KEY",
  "action": "bet-limit",
  "player_id": "player-1024",
  "provider": "pragmatic",
  "currency": "EUR",
  "min_minor": "10",
  "max_minor": "5000"
}

Both limits are required: send both as strings, or both as null to remove the limit.

Response#

{"status": "ok", "player": {…}}; betLimits shows the new limit. The object is described under get.

Errors#

See also#

• Bet limits: how player limits combine with project limits.
• Target outcomes and Free spins: how their rounds count.
• Admin: where project RTP settings and player levels are edited.