🔐 Authentication & Context
These settings apply to all API requests and WebSocket connections.
Choose manual token paste or interactive user login
Can use M2M token for demo purposes. In a real app, we would use the authenticated user's JWT token.
Only needed if JWT token does not include tenant claims.
Only needed if JWT token does not include tenant claims.
🧩 Subscription Group
👤 Subscriber
API: GET /api/messagebus/v1/subscribers | POST /api/messagebus/v1/subscribers
Recommended: Reuse an existing subscriber slug. A new subscriber will be created if the slug doesn't exist.
Unique identifier for this subscriber type (e.g., "pyxis-2.0", "mobile-app")
Only used when creating a new subscriber
🔎 Subscription Lookup
API: GET /api/messagebus/v1/subscriptions
Lookup an existing subscription by name and optional subscriber ID/slug, then populate the create form below.
📡 Create Subscription
API: POST /api/messagebus/v1/subscriptions
Create a new subscription or update the loaded lookup result.
Unique name for this subscription (include instance ID for non-shared)
Use * for single-level wildcard, # for multi-level
Durable survives disconnects; shared allows multiple subscribers to consume the same stream.
No active subscriptions
🔌 Subscribe via WebSocket
WebSocket: GET /api/messagebus/v1/messages/subscribe?subscriptionId={id}&token={ephemeral}
Note: Browsers cannot set Authorization headers on WebSocket connections. The JWT is exchanged for a single-use token through this app's backend.
Enter subscription ID from above or paste an existing one. Messages are auto-acknowledged.
📤 Publish Message
API: POST /api/messagebus/v1/messages/publish
If unchecked, returns immediately after sending the message to the underlying broker