Move a paused or failed sender's not-yet-contacted leads in this campaign onto the campaign's other available senders, evenly. Leads the sender already contacted stay pinned to it. Returns how many leads moved and how many receivers took them; receivers: 0 means no other sender was available and nothing moved (still 200). 422 when the account is not in the campaign's sender pool.
Authorization
bearerAuth An API key created under Settings → API & Webhooks.
In: header
Path Parameters
The sender account whose leads to move.
Response Body
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/campaigns/string/senders/string/rebalance"{ "data": { "moved": 0, "receivers": 0 }}List campaigns GET
Previous Page
Update a campaign PATCH
Updates any subset of a campaign's writable fields: `name`, `status` (set `active` to start sending, `paused` to stop), the sender pool (`linkedinAccountIds`), the outreach `sequence`, the send `schedule`, `aiInterestEnabled`, and the lead-exclusion rules (`excludeListIds` plus the `exclude*` flags). `sequence` and `schedule` are replaced wholesale — send the complete object you want, not a partial patch of it. Once a campaign has leads in progress, the `sequence` may only be edited safely: you can change step messages and delays and append new steps, but removing, reordering or retyping existing steps is rejected with `400` (a lead's progress is pinned to a step id). Duplicate the campaign to rework its sequence from scratch. An `active` campaign must keep at least one sender: sending an empty `linkedinAccountIds` while the campaign is (or is being set) `active` is rejected with `400`.