Route table

This is the complete surface of the broker binary, on its own page so it is linkable and searchable. It is not maintained by hand: the generator walks the Router::new() chain in server/src/main.rs, resolves each route’s required access level through route_access_level in server/src/auth.rs, and records whether the handler resolves a tenant. A route that does not exist in the code cannot appear here, and one that is added appears without anyone editing this page.

How to read the columns:

• Access level: the role set that satisfies the route. The levels are not a ladder; write-only and read-only are disjoint capabilities. The conventions page has the matrix, and the levels apply only when JWT_ENABLED is on.
• Tenant-scoped: whether the handler resolves a tenant identity and threads it into queue resolution. With native tenant scoping off (the default) every request resolves to one default tenant, and this column tells you which handlers would participate if it were on. Routes marked no are cell-wide reads or operator surfaces; that matters for multi-tenant deployments, covered in Self-hosting.
• Internal (broker-to-broker) routes are not a client API. They exist so brokers sharing a database can notify each other, and they require admin.
• Dashboard identity (broker-direct) is the small /auth surface the broker answers when it serves the dashboard itself. The routes are public by design; /auth/me enforces the auth state in its own handler. The dashboard page explains the standalone identity it returns.

The five message-plane routes have a page each documenting their request and response fields: push, pop, ack, transaction and lease extension. The remaining groups are documented on the other pages of this section.

Queen’s broker registers 63 method + path pairs. Every row below is read out of the router and the authorization table at build time.

Message plane

Queues and partitions

Consumer groups

Messages, DLQ and traces

Status, metrics and analytics

Streams

Operator surfaces

Dashboard identity (broker-direct)

Internal (broker-to-broker)

40 of these handlers resolve a tenant from the request; 11 /api/v1/* routes do not and are therefore cell-wide reads or operator surfaces.