The type of acknowledgment required by the Consumer

Where to start consuming messages on the stream

Allows push consumers to form a queue group

A unique name for a durable consumer Set name - for ephemeral consumers, also set idle_heartbeat

The consumer name

For push consumers this will regularly send an empty mess with Status header 100 and a reply subject, consumers must reply to these messages to control the rate of message delivery.

If the Consumer is idle for more than this many nanoseconds an empty message with Status header 100 will be sent indicating the consumer is still alive

The sequence from which to start delivery messages. Requires DeliverPolicy#StartSequence

The date time from which to start delivering messages Requires DeliverPolicy#StartTime

The rate at which messages will be delivered to clients, expressed in bytes per second

How messages are played back to the Consumer

Creates a consumer that is initially paused, but will resume at the specified Date and time. Specified as an ISO date time string (Date#toISOString()).