AsyncAPI channel · Bitfinex
· Bitfinex WebSocket API v2
/book
Aggregated order book channel. Subscription parameters:
`prec` (P0/P1/P2/P3/P4, default P0), `freq` (F0 realtime or F1
every 2s, default F0), `len` (1/25/100/250, default 25),
and optional client-defined `subId`. For funding books the
AMOUNT sign convention is inverted (negative = bid, positive
= ask).
Provider:BitfinexAsyncAPI: v2.6.0Spec: Bitfinex WebSocket API v2Operations: 2Messages: 8
Channel address
/book
Operations
publish
subscribeBook
subscribe
receiveBook
Messages
SubscribeBook
Subscribe (book)
Content-Type:
Unsubscribe
Unsubscribe from a channel
Content-Type:
TradingBookSnapshot
Aggregated trading book snapshot
Content-Type:
TradingBookUpdate
Aggregated trading book update
Content-Type:
FundingBookSnapshot
Aggregated funding book snapshot
Content-Type:
FundingBookUpdate
Aggregated funding book update
Content-Type:
ChecksumMessage
[CHANNEL_ID, "cs", CHECKSUM] - emitted when OB_CHECKSUM is enabled.
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.
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.