Skip to content

Trading

Build prediction-market interfaces on top of Parti Oracle. Route orders for your users, set your own builder fee, and give them access to every market on the platform.

You don't custody user keys, and you don't run infrastructure — the Parti signer, gateway, and matching engine handle the heavy lifting. You integrate the HTTP + WebSocket APIs.

What you get

  • One signer-managed trading keypair per user (you never hold private keys)
  • HMAC-authenticated request signing for your app-level API key
  • A builder fee (in bps) charged on every fill your users do, paid to a wallet you control
  • Real-time market-data and private order feeds over WebSocket
  • Full order lifecycle — post, cancel, cancel-replace, partial fills, IOC and GTC

Base URLs

Environment URL
Signer (mainnet) https://signer.parti-oracle.pbcapps.dev
API (mainnet) https://api.parti-oracle.pbcapps.dev
WebSocket (mainnet) wss://ws.parti-oracle.pbcapps.dev/v1/ws

How it works

Your Frontend  →  Parti Signer  →  Parti Gateway  →  Matching Engine
     │                 │
     │            Signs orders
     │            Manages user keys
     │
     └──  Reads market data directly from API (no auth needed)

You never handle private keys. The signer manages delegated keypairs for your users.

Fee Model

Fee Who Pays Where It Goes
Protocol fee (0.25–2%) Taker Parti treasury
Builder fee (you set, bps) Taker Your wallet
Maker rebate (0.5% default) n/a Resting maker

Set fee_bps on each order to earn your fee. It's charged on top of the protocol fee.

What's in this section

  • Quickstart — register, create a user key, place a first order in five steps
  • Authentication — HMAC request signing
  • Deposits — fund user accounts via the Solana bridge or Fogo native
  • Market Data — markets, order books, trades, candles
  • WebSocket — real-time price, trade, and private order feeds
  • API Reference — all builder endpoints