Declare a direct exchange and return a session-bound AMQPExchange handle.
Optionalname: string = "amq.direct"exchange name
Optionaloptions: ExchangeOptionsDeclare an exchange and return a session-bound AMQPExchange handle.
exchange name
exchange type: "direct", "fanout", "topic", "headers", or a custom type
Optionaloptions: ExchangeOptionsexchange declaration parameters and exchange arguments
Declare a fanout exchange and return a session-bound AMQPExchange handle.
Optionalname: string = "amq.fanout"exchange name
Optionaloptions: ExchangeOptionsDeclare a headers exchange and return a session-bound AMQPExchange handle.
Optionalname: string = "amq.headers"exchange name
Optionaloptions: ExchangeOptionsDeclare a queue and return a session-bound AMQPQueue handle.
The returned queue's subscribe uses auto-recovery and publish waits for
a broker confirm.
Subsequent calls with the same (non-empty) name return the cached handle
without redeclaring, and options on those calls are ignored.
Server-named queues (declared with "") are not cached or tracked for
auto-recovery: every call declares a fresh queue, and the broker assigns a
new name on every connection, so the old name is dead after a reconnect and
can't be recovered. Neither the queue nor its consumers are auto-recovered —
AMQPQueue.subscribe() recovery does not apply here. Re-declare such a queue
in an AMQPSessionOptions.onconnect handler — it runs again after every
reconnect — and bind/subscribe there.
queue name (use "" to let the broker generate a name)
Optionaloptions: QueueOptionsqueue declaration parameters and queue arguments
Perform an RPC call: publish a message and wait for the response. Creates a temporary client per call — simple and sufficient for most use cases.
For high-throughput scenarios where the per-call channel overhead matters, use rpcClient to create a reusable client instead.
The routing key / queue name of the RPC server
The request body
Optionaloptions: AMQPProperties & { timeout?: number }Optional AMQP properties and timeout
Optionaltimeout?: numberTimeout in milliseconds
The reply AMQPMessage
Create and start a reusable RPC client that keeps its channel open across multiple calls. Prefer rpcCall for simplicity; use this when you need to avoid the per-call channel overhead.
A started AMQPRPCClient ready for AMQPRPCClient.call invocations.
Create and start an RPC server that consumes from the given queue.
Each incoming message is passed to handler; the returned value is
published back to the caller's replyTo address.
Queue name to consume from
Callback that receives the decoded message, returns the response body
Optionalprefetch: numberChannel prefetch count (default: 1)
A started AMQPRPCServer
Stop the session: cancel reconnection, clear consumer tracking, and close the underlying connection.
Optionalreason: stringDeclare a topic exchange and return a session-bound AMQPExchange handle.
Optionalname: string = "amq.topic"exchange name
Optionaloptions: ExchangeOptionsStaticconnectConnect to an AMQP broker and return a session with automatic reconnection.
The transport is chosen from the URL scheme:
amqp:// / amqps:// → TCP socket (AMQPClient)ws:// / wss:// → WebSocket (AMQPWebSocketClient)Optionaloptions: AMQPSessionOptions<P, C, KP, KC>
High-level session with automatic reconnection and consumer recovery.
The generic parameters thread parser/coder type information through all session-owned handles (queues, exchanges, RPC clients/servers).
Users never write the generics explicitly — they're inferred from the
connect()call.Create via
AMQPSession.connect(url, options).