Count what needs attention
Returns how many leads sit in each bucket of the triage queue: waiting on a reply, due a catch-up, carrying a due task, gone quiet, stalled, or due to wake from on-hold. A lead lands in exactly one bucket, so the buckets sum to total.
/triage.getTriageCountsAuthorization
bearerAuth Enter your MailMoo API key (format: sk_live_...)
In: header
Response Body
application/json
application/json
application/json
curl -X GET "https://example.com/triage.getTriageCounts"{ "needs_reply": 0, "due_catchups": 0, "due_tasks": 0, "gone_quiet": 0, "stalled_evaluation": 0, "due_wakeups": 0, "total": 0, "property1": null, "property2": null}Change a campaign's senders POST
Adds senders to an existing campaign, removes some, or both in one call. Use the sender ids from campaigns.listSenders. Removing a sender unassigns the leads they held so the remaining senders pick them up, except leads already in conversation with that sender: they wait until moved to another sender with campaigns.leads.bulkChangeSender. A campaign always keeps at least one sender. Allowed while the campaign is running, and an added sender starts at once. A sender already on the campaign (to add) or not on it (to remove) is reported and ignored. Pass dryRun to see who would be added and removed and how many leads are affected, without changing anything.
List what needs attention GET
The whole triage queue as one paginated feed, already in priority order: people waiting on you first, then dates you set, then tasks you wrote, then leads that have gone silent. Each item carries the last message either way, so you can tell what is owed without opening the conversation.