Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.bayse.markets/llms.txt

Use this file to discover all available pages before exploring further.

​
New endpoints

​
Lookup user — GET /v1/user/lookup

Resolve a user’s tag (username) or ID to their public profile. Returns the user’s ID, tag, and avatar URL. Accepts either ?tag=mulumba or ?userId=<uuid>. Requires read authentication. See Lookup user for the full schema.

​
New WebSocket channel

​
User trades — user_trades

Subscribe to any user’s filled trade activity across all markets via /ws/v1/markets. No authentication required. 
{
  "type": "subscribe",
  "channel": "user_trades",
  "userId": "68eea9d8-a0fe-4534-ae88-b71e2f4f5c8f"
}
Broadcasts buy_order and sell_order events whenever the user’s orders are filled, regardless of the market engine (CLOB or AMM). The payload matches the existing activity feed format. See User trades for details.

​
Enhancements

​
engine and orderType in activity payloads

WebSocket activity broadcasts (buy_order, sell_order) now include two new fields in the order object:
  • engine — "CLOB" or "AMM". Indicates which market engine executed the trade.
  • orderType — "MARKET" or "LIMIT". Indicates the order type that produced the fill.
These fields appear on both the existing activity channel and the new user_trades channel.