WebSocket Channel Catalog#

This page enumerates every channel exposed on /v1/stream. For the wire protocol (subscribe / unsubscribe / ping / event frames) see the streaming concept; for the internal architecture see streaming architecture.

Endpoint & envelope#

wss://api.artery.questflow.ai/v1/stream?token=art_live_<your-key>

Every server-pushed message is one of:

jsonc// → subscribe ack
{ "type": "subscribed", "subscription_id": "sub_01HMQ5..." }
 
// → event frame
{
  "type": "event",
  "subscription_id": "sub_01HMQ5...",
  "data": {
    "type": "<channel-specific envelope type>",
    "provider": "polymarket" | "kalshi" | "hyperliquid_perp" | "hyperliquid_hip4",
    "marketId": "<provider market id or universalId>",
    "payload": { /* channel-specific */ },
    "receivedAt": 1747123338220
  }
}
 
// → heartbeat (every 30s)
{ "type": "pong" }
 
// → error
{ "type": "error", "error": "<message>" }

All channels require the stream scope. The admin scope grants implicit access to every channel including private user-trade feeds.

Channel categories#

Channel reference#

artery:stream:event:<universalId>#

Cross-platform spread snapshots for one universal event.

jsonc{
  "type": "event",
  "data": {
    "type": "event.spread",
    "provider": "polymarket",
    "marketId": "evt_01HMPKW8...",
    "payload": {
      "universalId": "evt_01HMPKW8...",
      "legs": [
        { "provider": "polymarket", "yesBid": 0.42, "yesAsk": 0.45, "yesMid": 0.435 },
        { "provider": "kalshi", "yesBid": 0.39, "yesAsk": 0.42, "yesMid": 0.405 }
      ],
      "fetchedAt": "2026-05-13T08:42:18Z"
    },
    "receivedAt": 1747123338220
  }
}

artery:stream:arbitrage:<universalId>#

Fires only when a profitable cross-provider or negation-pair arbitrage edge is detected on the latest spread snapshot.

Inspect payload.kind to distinguish: "cross_provider" has buyProvider / sellProvider; "negation_pair" has yesProvider / noProvider.

artery:stream:trade:<universalId>#

Public per-event trade fanout. Every observed fill across every linked market on this universal event.

jsonc{
  "type": "event",
  "data": {
    "type": "trade.observed",
    "provider": "polymarket",
    "marketId": "evt_01HMPKW8...",
    "payload": {
      "provider": "polymarket",
      "marketId": "0xCONDITION_ID",
      "ts": "2026-05-13T08:50:01.220Z",
      "side": "buy",
      "price": 0.421,
      "qty": 1500,
      "maker": "0xabc...",
      "taker": "0xdef...",
      "txHash": "0x123...",
      "logIndex": 4
    },
    "receivedAt": 1747123801222
  }
}

artery:stream:trade:<provider>#

Per-provider trade firehose. Same payload shape as the per-event channel, but unfiltered by event. Suitable for ETL pipelines.

artery:stream:user-trade:<orgId>#

Private per-org channel. Mirrors every fill where one of the org's bound wallets was maker or taker.

Subscribers to other orgs' channels receive { "type": "error", "error": "forbidden_scope" } on subscribe.

artery:stream:anomaly:<universalId>#

Per-event anomaly stream. Fires for all four kinds (trade_volume_spike, spread_widening, wallet_burst, settlement_delay) — filter client-side on payload.kind.

artery:stream:anomaly:<kind> (firehose)#

Global anomaly firehose, partitioned by kind:

Plus artery:stream:anomaly:all — every anomaly regardless of kind.

artery:stream:settlement_dispute:<universalId>#

UMA on-chain dispute observations for Polymarket-linked events.

Plus the provider-firehose alias artery:stream:settlement_dispute:polymarket.

artery:stream:settlement:<universalId>#

Fires once when a provider resolution for the event is observed (the authoritative payoff signal — typically Kalshi settled or HL HIP-4 resolveOutcome).

Downstream services (e.g. PnlFinalizationService) consume this to mark fills realized.

Raw upstream feeds (advanced)#

For callers that want the upstream payload pre-Artery-normalization:

The payload here is the upstream JSON shape, not Artery's normalized type. See per-provider notes in the streaming concept.

Subscription rules#

• Channels are flat strings — no glob expansion is supported in subscribe (use * only as the explicit channel suffix for provider firehoses).
• Multiple subscriptions are independent; unsubscribing one doesn't affect the others.
• Up to 1,000 active subscriptions per connection (subscription_limit error on overflow).
• Concurrent connections per key follow your tier table.

Backpressure#

See also#

• Streaming concept — wire protocol overview
• Streaming architecture — leader-lock + pub/sub internals
• Streaming quickstart recipe — connect, subscribe, parse
• Examples — one-shot CLI test