RebindV1Request
Note
This page was generated by extracting information from a JSON Schema data file for the API. It may be missing some information, or otherwise suggest approximate or placeholder values based on information in the schema file; this is due to limitations on how that data is extracted from the underlying Rust code and into the JSON Schema, and then again from there and into these docs.
Describes which messages should be rebound. The criteria apply to the scheduled queue associated with a given message.
This is an object value, with the following properties:
-
always_flush- optionalboolean. If true, make all matched messages immediately eligible for delivery. When false, (the default), only messages whose queue has changed will be made immediately eligible. -
campaign- optional nullablestring. The campaign name to match. If omitted, any campaign will match. -
data- requiredobject. The data, a json object with string keys AND values to pass to the rebind operation -
domain- optional nullablestring. The domain name to match. If omitted, any domain will match. -
reason- requiredstring. Reason to log in the delivery log. Each matching message will log with an AdminRebind record unless you suppress logging. -
routing_domain- optional nullablestring. The routing_domain name to match. If omitted, any routing_domain will match. -
suppress_logging- optionalboolean. If true, do not generate AdminRebind delivery logs for matching messages. -
tenant- optional nullablestring. The tenant to match. If omitted, any tenant will match. -
trigger_rebind_event- optionalboolean. If true, arebindevent will be triggered and passed each message and the supplied data. If false, no event will be triggered and each field in data will be applied to the msg metadata, overwriting any previous value for that key.