Skip to content
Arenaton Docs

API Reference

REST Sketch

Section titled “REST Sketch”
GET  /api/markets
GET  /api/markets/{marketId}
GET  /api/markets/{marketId}/book
GET  /api/markets/{marketId}/trades
GET  /api/markets/{marketId}/rules


POST /api/orders
POST /api/orders/{orderId}/cancel
POST /api/orders/cancel-all
GET  /api/accounts/{address}/portfolio
GET  /api/accounts/{address}/orders
GET  /api/accounts/{address}/trades
GET  /api/accounts/{address}/redeemable
GET  /api/markets/{marketId}/redemption


POST /api/paper/faucet/claim
GET  /api/paper/markets
GET  /api/paper/markets/{marketId}
GET  /api/paper/markets/{marketId}/book
GET  /api/paper/markets/{marketId}/trades
GET  /api/paper/markets/{marketId}/rules
GET  /api/paper/accounts/{address}/portfolio
GET  /api/paper/accounts/{address}/positions
GET  /api/paper/accounts/{address}/fills
POST /api/paper/orders
POST /api/paper/orders/{orderId}/cancel
POST /api/paper/settlement/run
POST /api/paper/markets/{marketId}/live-events/simulate
POST /api/paper/markets/{marketId}/close
POST /api/paper/markets/{marketId}/resolve
POST /api/paper/markets/{marketId}/resolution/finalize
POST /api/paper/markets/{marketId}/redeem
GET  /api/paper/status
WS   /api/paper/ws


GET  /api/contract-registry
GET  /api/paper/contract-registry
GET  /api/status

WebSocket Sketch

Section titled “WebSocket Sketch”
WS /ws


market:{marketId}:book
market:{marketId}:trades
market:{marketId}:status
market:{marketId}:live-state
paper:status
account:{address}:orders
account:{address}:fills
account:{address}:portfolio

Paper WebSocket events use concrete event names while the production channel contract is still maturing:

paper_market_book
paper_matched_pending_fill
paper_settlement_confirmed
paper_account_positions
paper_market_lifecycle
paper_redemption_confirmed
paper_market_live_state
paper_status

Settlement And Portfolio Semantics

Section titled “Settlement And Portfolio Semantics”
  • matchedPending fills are not confirmed Outcome Shares.
  • Settlement confirmation is required before portfolio positions appear.
  • Primary binary matching creates YES/NO Outcome Shares through CTF Collateral splitting.
  • Secondary resale transfers existing Outcome Shares.
  • Redeemable Markets appear only after final resolution.
  • Redemption APIs must prepare direct CTF redemption data, not a claim against an Arenaton balance.

Public Market Data

Section titled “Public Market Data”

Public APIs should expose market list/detail, best bid/ask, recent trades, volume, open interest, resolution source, market status, and selected WebSocket updates.

Private account APIs require authentication and must enforce geo/risk restrictions for trading actions.

External CTF Market Data

Section titled “External CTF Market Data”

Arenaton can consume public third-party CTF market data for browsing and research surfaces. External market-data APIs must not become Arenaton order intake, settlement authority, or registry configuration.

GET  /markets              — List all active CTF markets (up to 500)
GET  /market?condition_id= — Single market details
GET  /book?token_id=       — Order book for a token
POST /prices               — Batch prices for up to 500 token IDs

WS wss://ws-subscriptions-clob.polymarket.com/ws/market

Third-party contract addresses are references only. Arenaton clients must read live addresses from /api/contract-registry or /api/paper/contract-registry. See Gnosis CTF Model for the contract-boundary rules.

Compatibility Routes

Section titled “Compatibility Routes”

The pulse server still exposes compatibility routes for current health checks, event data, and GraphQL probes while the exchange API matures.