System Status - PolySimulator

GET

status

System Status

curl --request GET \
  --url https://api.polysimulator.com/v1/status

{
  "status": "<string>",
  "timestamp": "<string>",
  "database": {},
  "redis": {},
  "matching_engine": {},
  "websocket": {},
  "markets": {},
  "version": "1.0.0",
  "uptime_seconds": 123
}

Response

Successful Response

status

string

required

timestamp

string

required

database

Database · object

required

redis

Redis · object

required

matching_engine

Matching Engine · object

required

websocket

Websocket · object

required

markets

Markets · object

required

version

string

default:1.0.0

uptime_seconds

number | null

Get Api MeGet the authenticated user's profile and account balance. Accepts both ``X-API-Key`` and ``Authorization: Bearer <jwt>`` authentication. Useful as a quick connectivity test and to retrieve balance without hitting the full /v1/account/balance endpoint. The ``permissions`` field reflects the scope of the AUTHENTICATING key (e.g. ``["read", "trade"]`` or ``["read"]`` for a free-tier / read-only key), so a developer can inspect what their key can do without parsing the keys endpoint. For Bearer-JWT (dashboard) auth there is no API key, so the documented default scope is returned. Per-user 5s Redis cache (override via ``ME_CACHE_TTL_S`` env). Set TTL to 0 to disable. Cache de-amplifies the 2-DB-query body — the pool was exhausting at c=50 sustained because every authed request held a session for ~150-300ms (launch-eve perf RCA, F-2).

System Status

curl --request GET \
  --url https://api.polysimulator.com/v1/status

{
  "status": "<string>",
  "timestamp": "<string>",
  "database": {},
  "redis": {},
  "matching_engine": {},
  "websocket": {},
  "markets": {},
  "version": "1.0.0",
  "uptime_seconds": 123
}