Funding rate

Funding readouts for perpetual/dated swaps, latest-wins, carrying the full template surface — current rate and boundary, interval, predicted next rate, settled rate, exchange bounds, premium and interest-rate components, collection method and settlement state.

URL wss://marketdata.immix.xyz/

Topic funding.{symbol}

Topic parameter	Description
`symbol`	refdata’s canonical symbol — derivatives in ccxt spelling BASE/QUOTE:SETTLE, e.g. OKX@BTC/USDT:USDT (there is no :SWAP form)

Request parameters

Parameter	Type	Required	Description
`op`	string	Yes	`subscribe`
`reqId`	string	No	client correlation id, echoed verbatim on the ack
`params`	object	Yes
> `topics`	array of strings	Yes	the dotted topic string, e.g. trade.OKX@BTC/USDT or candlestick.OKX@BTC/USDT.ONE_MINUTE.250ms

Response parameters

Parameter	Type	Required	Description
`op`	string	Yes	One of `auth`, `subscribe`, `unsubscribe`, `error`.
`reqId`	string	No
`success`	boolean	Yes
`error`	string	No	One of `auth_required`, `invalid_token`, `unknown_op`, `malformed`, `too_many_topics`.
`topics`	array of objects	No	answers ride in request order — the correlator for entries whose topic could not compose (error rows echo the composed topic best-effort, absent parts empty)
> `topic`	string	Yes
> `state`	string	Yes	live: data flows now (latest-image lanes — tob, mark, funding, oi, ticker — answer live whether or not an image is held yet; the first image flows on arrival). syncing (book topics): the gateway holds no synced book yet — the snapshot is pushed unprompted the moment it syncs, at latest one connector restate interval. error on a plain (string-topic) row, no code: the topic composed nothing, and it never arms retroactively. Either the channel is outside the vocabulary or the tier suffix is outside the configured set (an unrecognized suffix reads as part of the symbol) — correct the topic — or the symbol is unknown to the gateway’s refdata fold (derivative symbols are refdata’s ccxt spelling BASE/QUOTE:SETTLE, e.g. OKX@BTC/USDT:USDT — there is no :SWAP form) — resubscribe once refdata holds the instrument. Composite rows: live iff every enabled source book is synced, stated within the topic’s output scales, AND every required FX pair is current (the full image pushes immediately); syncing otherwise, kept by the first tick at which the composite becomes computable — a source out for precision is named by a degraded frame at that tick, since syncing alone does not say it; a composite error row carries code. One of `live`, `syncing`, `error`, `unsubscribed`, `not_subscribed`.
> `priceScale`	integer	No	composite live/syncing rows only — the resolved output price scale (max over all configured sources’ reference records, disabled included), bounding the fractional digits any price on the topic can carry; never padding. It holds until a status rescaled frame on the topic restates it
> `qtyScale`	integer	No	composite rows only — the resolved output qty scale; as priceScale
> `code`	string	No	composite error rows only — the closed vocabulary clients parse; every validation failure maps to exactly one code. One of `unknown_channel`, `bad_name`, `bad_tier`, `tier_required`, `name_in_use`, `unknown_instrument`, `duplicate_source`, `mixed_base_asset`, `unit_mismatch`, `bad_normalisation`, `bad_depth`, `bad_ladder`, `too_many_sources`, `budget_exceeded`, `malformed`.
> `message`	string	No	supplementary human text naming the offending source or field — never something a client parses

Push data parameters

Parameter	Type	Required	Description
`event`	string	Yes	`funding`
`topic`	string	Yes
`seq`	string	Yes	the envelope’s global sequence, as a decimal string
`seqTs`	string	Yes
`data`	object	Yes	the full 14-field funding payload — 13 funding values plus exchTs; rates are exact decimals at the schema’s fixed 1e-8 rate scale; absent optionals (and an unstated interval or vocabulary) are null
> `rate`	string	Yes	the rate settling at fundingTs
> `fundingTs`	string	Yes	the upcoming settlement boundary, epoch ns
> `intervalMinutes`	integer, nullable	Yes
> `predictedRate`	string, nullable	Yes	the exchange-predicted rate for the next period
> `nextFundingTs`	string, nullable	Yes
> `settledRate`	string, nullable	Yes	the realized rate of the most recent past boundary
> `settledTs`	string, nullable	Yes
> `minRate`	string, nullable	Yes
> `maxRate`	string, nullable	Yes
> `premium`	string, nullable	Yes
> `interestRate`	string, nullable	Yes
> `method`	string, nullable	Yes	the exchange’s funding collection mode. One of `current_period`, `next_period`.
> `settState`	string, nullable	Yes	whether settledRate is final. One of `processing`, `settled`.
> `exchTs`	string	Yes

Behaviour

Absent optionals are JSON null. Subscribing pushes the current readout immediately when held.

Request — sent

{
  "op": "subscribe",
  "params": {
    "topics": [
      "funding.{symbol}"
    ]
  }
}

Response — received

{
  "op": "subscribe",
  "success": true,
  "topics": [
    {
      "topic": "funding.{symbol}",
      "state": "live"
    }
  ]
}

Push data — received

{
  "event": "funding",
  "topic": "funding.{symbol}",
  "seq": "<string>",
  "seqTs": "<string>",
  "data": {
    "rate": "<string>",
    "fundingTs": "<string>",
    "intervalMinutes": 0,
    "predictedRate": "<string>",
    "nextFundingTs": "<string>",
    "settledRate": "<string>",
    "settledTs": "<string>",
    "minRate": "<string>",
    "maxRate": "<string>",
    "premium": "<string>",
    "interestRate": "<string>",
    "method": "current_period",
    "settState": "processing",
    "exchTs": "<string>"
  }
}

Each frame is its shape, read off the contract: <string> stands for a value, and a union shows its first form.