AsyncAPI channel · Apache Pulsar · Apache Pulsar Messaging API

`non-persistent/{tenant}/{namespace}/{topic}`

Name: non-persistent/{tenant}/{namespace}/{topic}
Creator: Apache Pulsar

A non-persistent Pulsar topic. Messages are not stored to disk and are only delivered to currently connected consumers. Offers lower latency at the cost of durability.

Open source AsyncAPI → All Apache Pulsar channels Apache Pulsar provider profile

Provider: Apache Pulsar AsyncAPI: v2.6.0 Spec: Apache Pulsar Messaging API Operations: 2 Messages: 1

Channel address

non-persistent/{tenant}/{namespace}/{topic}

Parameters

tenant —
namespace —
topic —

Operations

publish

produceNonPersistentMessage

Produce a message to a non-persistent topic

consumeNonPersistentMessage

Consume from a non-persistent topic

Messages

PulsarMessage

A message in Apache Pulsar

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.