Session Management API

Start, restart and stop sessions programmatically. These endpoints authenticate with your API key, verify session ownership, and publish launch/cancel commands to your connected client via Redis SSE.

Base URL: https://api.b337.ai

Start Session

Launch a session. The command is delivered to your connected client in real time via SSE.

POST /api/start_session

Request Body

Parameter	Type	Required	Description
session_id	string	Yes	The session ID to launch

Request

curl -X POST https://api.b337.ai/api/start_session \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"session_id": "abc-123"}'

Python

import requests

response = requests.post(
    "https://api.b337.ai/api/start_session",
    headers={
        "X-API-Key": "YOUR_API_KEY",
        "Content-Type": "application/json",
    },
    json={"session_id": "abc-123"},
)

print(response.json())

Response

{
  "status": "success",
  "session_status": "launching",
  "delivered": true
}

Restart Session

Cancels a running session and immediately re-launches it.

POST /api/restart_session

Request Body

Parameter	Type	Required	Description
session_id	string	Yes	The session ID to restart

Request

curl -X POST https://api.b337.ai/api/restart_session \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"session_id": "abc-123"}'

Python

import requests

response = requests.post(
    "https://api.b337.ai/api/restart_session",
    headers={
        "X-API-Key": "YOUR_API_KEY",
        "Content-Type": "application/json",
    },
    json={"session_id": "abc-123"},
)

print(response.json())

Response

{
  "status": "success",
  "session_status": "launching",
  "delivered": true
}

Stop Session

Stops one of your own running sessions. Stopping is never blocked by your subscription status, so you can always stop a running bot.

POST /v3/stop_session

Request Body

Parameter	Type	Required	Description
session_id	string	Yes	The session ID to stop
revoke	bool	No	Default `false`. If `true`, the stop also reaches a client that is offline right now: it stops the session as soon as it reconnects. The flag is cleared by your next start of that session

Request

curl -X POST https://api.b337.ai/v3/stop_session \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"session_id": "abc-123"}'

Python

import requests

response = requests.post(
    "https://api.b337.ai/v3/stop_session",
    headers={
        "X-API-Key": "YOUR_API_KEY",
        "Content-Type": "application/json",
    },
    json={"session_id": "abc-123"},
)

print(response.json())

Response

{
  "status": "stopped",
  "session_id": "abc-123",
  "delivered": true
}

delivered: false means your desktop client is not connected, so the stop did not reach it live. Send "revoke": true to make sure it stops when it reconnects.

Response Fields

Field	Type	Description
status	string	Start/restart: `"success"` or `"error"`. Stop: `"stopped"`
session_status	string	Start/restart only. The session's new status (e.g. `"launching"`)
session_id	string	Stop only. The session that was stopped
delivered	bool	Whether the command was delivered to a connected client. `false` means no client is currently connected via SSE

How It Works

Authentication - Your X-API-Key header is validated
Ownership verification - The API confirms the session belongs to your account via verify_session_ownership
Session data - Full session data is fetched via get_complete_session_data
Command delivery - A launch (start), cancel + launch (restart) or cancel (stop) command is published to your client via Redis SSE
Response - Returns the result and whether the command was delivered

Error Responses

Status Code	Description
400	Stop only: body is not JSON, or `session_id` is missing
401	Invalid or missing API key
403	Session does not belong to your account, or (start/restart only) your account has no active subscription
404	Session not found
500	Internal server error

Error Response Example:

{
  "status": "error",
  "message": "Session not found"
}

Notes

The delivered field indicates real-time delivery status. If false, your desktop client is not connected - the session will not start until a client connects
Restart performs a cancel followed by a launch in sequence
Stop works with or without an active subscription, so a lapsed account can always stop a running bot
A plain stop does not block a later start. Only "revoke": true keeps an offline client from resuming, and your next start clears it
These endpoints are rate-limited per API key

Next Steps

Sessions - Understand session lifecycle
Place Bet - Place racing & sports bets