Attaches a rule (cadence, retry interval, working hours, escalation) to the campaign. The underlying schema is many-to-many but every code path treats it as one-rule-per-campaign, so this endpoint REPLACES any previously attached rule via sync(). Important caveat: changing the rule on a running (‘In Process’) campaign does NOT retroactively rebuild already-scheduled tasks — they still reflect the OLD cadence. New tasks created after the change (via add-contacts-to-pool, attach-pool, or republish) will use the new rule. For a hard reset on running campaigns, the safe sequence is: stop the campaign → assign new rule → publish again.
Documentation Index
Fetch the complete documentation index at: https://developers.mindhunters.ai/llms.txt
Use this file to discover all available pages before exploring further.
Use a Bearer token to access these API endpoints. Example: "Bearer {your-token}"
UUID of the campaign to assign the rule to.
UUID of the rule to attach. Create rules with POST /api/v1/rules. The rule's type ('call'/'text') should generally match the campaign's communication channel — text rules force one-shot semantics, call rules support multi-attempt cadence.