AsyncAPI channel · Blockchain.com · Blockchain.com WebSocket APIs

/inv#addr_sub

Stream of transactions involving a specific Bitcoin address. The `addr` parameter is required and identifies the address being watched. Subscribe with `{"op":"addr_sub","addr":"$bitcoin_address"}`; unsubscribe with the matching `addr_unsub`.

Open source AsyncAPI → All Blockchain.com channels Blockchain.com provider profile
Provider: Blockchain.com AsyncAPI: v2.6.0 Spec: Blockchain.com WebSocket APIs Operations: 2 Messages: 3

Channel address

/inv#addr_sub

Parameters

Operations

publish
subscribeAddress
Subscribe / unsubscribe to transactions for a specific Bitcoin address.
receiveAddressTx
Receive utx events for transactions involving the subscribed address.

Messages

BitcoinOpAddrSub
Subscribe to address activity
Content-Type:
BitcoinOpAddrUnsub
Unsubscribe from address activity
Content-Type:
BitcoinUtxMessage
Unconfirmed transaction (utx)
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.