AsyncAPI channel · Arkham Intelligence
· Arkham Intelligence Transfers WebSocket API
/ws/transfers
Bidirectional stream for managing transfer subscriptions and receiving matching transfer notifications. Authentication uses the `API-Key` header during the WebSocket handshake.
Channel address
/ws/transfers
Operations
publish
clientCommands
Messages a client sends to the server.
subscribe
serverEvents
Messages the server sends to the client.
Messages
subscribe
Create a new filter to receive matching transfers in real time. Filters must include at least one of `from`, `to`, `tokens`, `base`, or `usdGte >= 10,000,000`.
Content-Type:
unsubscribe
Remove an existing filter by its server-assigned filter ID.
Content-Type:
reconnect
Restore a previous WebSocket session within five minutes of disconnection using its session ID.
Content-Type:
transfer
A matching blockchain transfer for an active filter.
Content-Type:
ack
Acknowledgment for a successful client operation (subscribe, unsubscribe, reconnect).
Content-Type:
error
Error notification, including rate-limit and authentication errors.
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.