AsyncAPI channel · HiveMQ · HiveMQ MQTT Broker

{topic}

Generic MQTT application topic. MQTT topics are UTF-8 strings organised as hierarchical levels separated by `/`. Wildcards `+` (single level) and `#` (multi level) are valid only in subscriptions. The actual topic tree is defined by the application that uses HiveMQ.

Open source AsyncAPI → All HiveMQ channels HiveMQ provider profile
Provider: HiveMQ AsyncAPI: v2.6.0 Spec: HiveMQ MQTT Broker Operations: 2 Messages: 1

Channel address

{topic}

Parameters

Operations

publish
publishToTopic
Publish a message to an MQTT topic.
subscribeToTopic
Subscribe to an MQTT topic or topic filter.

Messages

MqttApplicationMessage
An MQTT PUBLISH payload. Payload is opaque to the broker; HiveMQ forwards bytes unchanged. MQTT 5 adds user properties, payload format indicator, content type, response topic, and correlation data whi
Content-Type: application/octet-stream

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.