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.
Provider:SignalAsyncAPI: v2.6.0Spec: Signal Server Real-Time EventsOperations: 1Messages: 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.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
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.