AsyncAPI channel · Red5
· Red5 Pro WebRTC Streaming Events
/subscribe
WebSocket channel for a subscriber to establish a WebRTC session and receive a live stream from the Red5 Pro server. The subscriber sends an SDP offer and ICE candidates; the server responds with an SDP answer and its ICE candidates.
Provider:Red5AsyncAPI: v2.6.0Spec: Red5 Pro WebRTC Streaming EventsOperations: 2Messages: 5
Channel address
/subscribe
Operations
publish
subscriberSend
Subscriber sends signaling message to server
subscribe
subscriberReceive
Subscriber receives signaling message from server
Messages
SdpOffer
WebRTC SDP offer from a client
Content-Type:
IceCandidate
ICE candidate for WebRTC peer connection establishment
Content-Type:
SubscribeRequest
Initial request from a subscriber to join a streaming session
Content-Type:
SdpAnswer
WebRTC SDP answer from the server
Content-Type:
StreamEvent
Server-sent event about stream state changes
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.
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.