AsyncAPI channel · Bitquery · Bitquery Streaming GraphQL Subscriptions

/

The single GraphQL-over-WebSocket channel exposed by Bitquery. All subscription operations (DEX trades, transfers, blocks, transactions, mempool transactions, contract events, balance updates, etc.) are multiplexed over this one channel using GraphQL protocol envelopes. The actual data shape is determined by the GraphQL document sent in the `subscribe` (or `start`) message payload.

Open source AsyncAPI → All Bitquery channels Bitquery provider profile
Provider: Bitquery AsyncAPI: v2.6.0 Spec: Bitquery Streaming GraphQL Subscriptions Operations: 2 Messages: 11

Channel address

/

Operations

publish
sendClientFrames
Client-to-server GraphQL protocol frames.
receiveServerFrames
Server-to-client GraphQL protocol frames.

Messages

connection_init
First frame the client sends after the WebSocket opens.
Content-Type:
subscribe
Starts a new GraphQL subscription, identified by `id`.
Content-Type:
start
Legacy `subscriptions-transport-ws` form of `subscribe`. Identical payload, different `type`.
Content-Type:
ping
Optional ping frame.
Content-Type:
complete
Terminates a single subscription identified by `id`. Sent by the server when the subscription naturally ends or by the client to stop it. Bitquery does not acknowledge legacy `stop` messages, so clien
Content-Type:
connection_ack
Server acknowledgement that the connection is initialised.
Content-Type:
next
A subscription result pushed to the client.
Content-Type:
data
Legacy form of `next`.
Content-Type:
ka
Periodic keep-alive frame the server emits on the `graphql-ws` subprotocol so clients can detect a silent disconnect.
Content-Type:
pong
Pong frame, emitted in response to a `ping` or as a heartbeat to keep the connection alive on the `graphql-transport-ws` subprotocol.
Content-Type:
error
Subscription-scoped GraphQL error frame.
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 Agent Skill and MCP server surfaces of the same providers.

Work with this as data

Every channel here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for event channels

4 MCP tools reach this
  • find_channelsBrowse and filter every channel in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This channel 
curl "https://apis.io/api/v1/channels/untitled"
All event channels 
curl "https://apis.io/api/v1/channels?limit=25"

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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.