Send the same customer-visible reply to every ticket in the selection. Unlike bulk updates there is NO fast path — every reply runs the full createComment pipeline (channel/email delivery, notifications, SLA clearing, workflows, integrations). Selections up to 30 send inline; larger ones (up to 500) fan out as per-ticket scheduled replies firing ~60s later, delivered by the Bull worker with the reconcile-sweep backstop and cancellable per ticket until they fire.
Bearer <token>.Explicit ticket ids (checkbox selection).
"All matching" — the same raw query-param shape the lane's GET /tickets uses.
Select-N: only the first N tickets in the query's sort order. Query mode only.
TipTap JSON document — same shape as a single reply's comment.
Client-generated idempotency key. Retries with the same batchId never
double-send: every created comment is deduped per ticket via
data.clientMutationId = bulkreply_<batchId>_<ticketId>.
Ok