Sessions
session.updateBetSettings
Changes a player’s bet settings during play.
Who calls it
You → us
POST /v1/session.updateBetSettingsThe player levelled up, or a limit changed. Sign the call with your API key. See Authentication.
Request
| Field | Type | What it is |
|---|---|---|
requestId | string | Your id for this change. Send it again after a timeout and you get the first answer back. |
firstSentAt | string, UTC time | When you first sent this request. It stays the same on every retry. A request older than 7 days is refused. |
sessionId | string | Which player’s game. |
betSettings | object | The new min, max and default. |
betSettings.version | integer | Goes up with each change. A late retry of an old change is ignored, so an old limit never comes back. |
Answer
An ok answer. A round already open keeps its bet. The next round uses the new settings.
Errors
| Code | When | Your next step |
|---|---|---|
session_not_found | No session with this sessionId in this environment. | Check the id and the Environment header. |
session_closed | session.updateBetSettings on a closed session. | Nothing. The player’s next start gets the new settings. |
bet_settings_invalid | min is above max, default is outside them, or a value is 0 or less. | Fix the bet settings. |
invalid_request | A field is missing or wrong, for example a firstSentAt more than 5 minutes in the future. message names the field. | Fix the call. Sending it again unchanged fails again. |
request_expired | firstSentAt is older than 7 days. Nothing is done. | A bug or a stuck job on your side. Look up the result with session.get or round.get. |
duplicate_mismatch | A requestId we have seen comes with a different body. | A bug on your side: each new change needs a new id. |
Every call can also return the codes that guard all calls. See Error codes.
Example
Request
{
"requestId": "rq-77188",
"firstSentAt": "2026-10-31T09:30:00Z",
"sessionId": "s-01JC8Z…",
"betSettings": { "version": 2, "min": 10, "max": 20000, "default": 100 }
}
Answer
{ "ok": true, … }