A VTN-assigned MQTT topic carrying notifications for one object type and one operation (or ALL). Resolve the concrete name from notifierTopicsResponse.topics.{CREATE|UPDATE|DELETE|ALL} returned by the matching GET /notifiers/mqtt/topics/* operation. The specification example pattern is "{objectType}s/create", "{objectType}s/update", "{objectType}s/delete", "{objectType}s/+", but a VTN may name top
topic — Runtime-resolved topic name from the notifier topics endpoints.
Operations
receive
receiveMqttNotification
The subscriber consumes JSON-serialized notifications from a VTN-assigned topic. Target-based filtering is not available on this binding; object privacy is enforced by VEN-scoped topics instead.
Messages
objectOperationNotification
VTN generated object included in request to subscription callbackUrl.
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.