AsyncAPI channel · Signal · Signal Server Real-Time Events

/v1/websocket/provisioning

The provisioning WebSocket channel used during the device linking flow. A new device connects to this channel and receives a provisioning UUID. The primary device then sends an encrypted provisioning message containing the account identity key and other credentials needed to complete the linking process.

Open source AsyncAPI → All Signal channels Signal provider profile
Provider: Signal AsyncAPI: v2.6.0 Spec: Signal Server Real-Time Events Operations: 1 Messages: 2

Channel address

/v1/websocket/provisioning

Operations

publish
receiveProvisioningMessages
Receive provisioning messages during device linking

Messages

ProvisioningUUID
The server assigns a provisioning UUID to a new device during the device linking process.
Content-Type: application/json
ProvisioningMessage
An encrypted provisioning message from the primary device containing account credentials for the new linked device.
Content-Type: application/json

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.