Sessions
session.close
Closes one session.
Who calls it
You → us
POST /v1/session.closeCall it when the player logs out or leaves. 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 session. |
reason | string | Your own text, for example logout. Both sides can later see why it closed. |
Answer
ok, with the session as it is. Closing a session that is already closed is not an error. The answer says who closed it first and why. A close that crossed our own close must not look like a failure.
After a close
- The session accepts nothing more from the player.
- Open rounds still finish and pay.
- A Mines round still open stays open for the player’s next session, or finishes by time.
- We send
session.closedto your server, for every close.
Errors
| Code | When | Your next step |
|---|---|---|
session_not_found | No session with this sessionId in this environment. | Check the id and the Environment header. |
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. This call never counts against your rate limits.
Example
Request
{
"requestId": "rq-77190",
"firstSentAt": "2026-10-31T09:40:00Z",
"sessionId": "s-01JC8Z…",
"reason": "logout"
}
Answer
{ "ok": true, … }