Returns one consumer's configuration and delivery state.

GET /v1/mq/stream/{stream}/consumer/{name}

MQ → · All API references → · Six flows, four surfaces →


Address	`https://api.hanzo.ai/v1/mq/stream/{stream}/consumer/{name}`
Method	`GET`
Operation	`get_mq_stream_by_stream_consumer_by_name`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Request

2 fields.

Field	In	Type	Required	Description
`stream`	path	string	yes	Stream is the stream name, from the path.
`name`	path	string	yes	Name is the consumer name, from the path.

Response

Status	Body	Meaning
`200`	Consumer	ok

200 body — 25 fields.

Field	In	Type	Always	Description
`ack_floor`	body	Sequences	—
`ack_floor.consumer_seq`	body	integer	—	Consumer is the consumer's own sequence.
`ack_floor.stream_seq`	body	integer	—	Stream is the corresponding stream sequence.
`config`	body	Durable	—
`config.ack_policy`	body	string	—	Ack is the acknowledgment policy: explicit (default), all, or none.
`config.ack_wait`	body	string	—	AckWait is how long the broker waits for an ack before redelivering, e.g.
`config.deliver_policy`	body	string	—	Deliver is where delivery starts: all (default), last, new, by_start_sequence, by_start_time, or last_per_subject.
`config.description`	body	string	—	Description says what this consumer is for.
`config.durable_name`	body	string	—	Name is the durable consumer name (alphanumeric, hyphens, underscores).
`config.filter_subject`	body	string	—	Filter delivers only messages on this org-relative subject (wildcards supported).
`config.max_ack_pending`	body	integer	—	MaxAckPending caps unacknowledged messages in flight (default 1000).
`config.max_deliver`	body	integer	—	MaxDeliver caps delivery attempts per message; -1 (default) is unlimited.
`config.opt_start_seq`	body	integer	—	StartSeq is the starting sequence for deliver_policy by_start_sequence.
`config.opt_start_time`	body	string (date-time)	—	StartTime is the starting instant for deliver_policy by_start_time.
`config.replay_policy`	body	string	—	Replay is the replay pacing: instant (default) or original.
`created`	body	string (date-time)	—	Created is when the consumer was created.
`delivered`	body	Sequences	—
`delivered.consumer_seq`	body	integer	—	Consumer is the consumer's own sequence.
`delivered.stream_seq`	body	integer	—	Stream is the corresponding stream sequence.
`name`	body	string	—	Name is the consumer name.
`num_ack_pending`	body	integer	—	AckPending is the number of delivered, not yet acknowledged messages.
`num_pending`	body	integer	—	Pending is the number of messages yet to be delivered.
`num_redelivered`	body	integer	—	Redelivered is the number of messages currently being redelivered.
`num_waiting`	body	integer	—	Waiting is the number of pull requests waiting for messages.
`stream_name`	body	string	—	Stream is the stream this consumer reads.

Failure carries the platform error shape — see Errors.

Examples

hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.

import { Configuration, MqApi } from 'hanzoai';

const api = new MqApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getMqStreamByStreamConsumerByName({ stream: 'stream', name: 'name' });

from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import MqApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = MqApi(client).get_mq_stream_by_stream_consumer_by_name(stream='stream', name='name')

cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)

resp, _, err := client.MqAPI.GetMqStreamByStreamConsumerByName(context.Background()).Execute()
if err != nil {
	return err
}

use hanzo_cloud::apis::{configuration::Configuration, mq_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = mq_api::get_mq_stream_by_stream_consumer_by_name(&cfg, Default::default()).await?;

import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.MqApi;

ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));

var result = new MqApi(client).getMqStreamByStreamConsumerByName();

The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →

curl https://api.hanzo.ai/v1/mq/stream/<stream>/consumer/<name> \
  -H "Authorization: Bearer $HANZO_API_KEY"

The door reaches mq through the mq tool, which names its 15 operations with its own verbs — this one among them, under a name only the door declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "get_mq_health"
         }
       }
     }'

MQ API · All Hanzo APIs · Interactive reference

Returns one consumer's configuration and delivery state.

Request

Response

Examples

On this page