AsyncAPI channel · Bitfinex · Bitfinex WebSocket API v2

/candles

Candles channel. Subscribe with a key of the form `trade:TIMEFRAME:SYMBOL` (or `trade:TIMEFRAME:SYMBOL:aAGGR:pPER_START:pEND` for funding). Supported timeframes: 1m, 5m, 15m, 30m, 1h, 3h, 6h, 12h, 1D, 1W, 14D, 1M.

Open source AsyncAPI → All Bitfinex channels Bitfinex provider profile
Provider: Bitfinex AsyncAPI: v2.6.0 Spec: Bitfinex WebSocket API v2 Operations: 2 Messages: 5

Channel address

/candles

Operations

publish
subscribeCandles
receiveCandles

Messages

SubscribeCandles
Subscribe (candles)
Content-Type:
Unsubscribe
Unsubscribe from a channel
Content-Type:
CandlesSnapshot
Candles snapshot
Content-Type:
CandleUpdate
Candle update
Content-Type:
Heartbeat
[CHANNEL_ID, "hb"] - sent every 15 seconds of inactivity.
Content-Type:

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.