Sending Status
Resume Sending
Restore paused sending after fixing the cause of the bounces
POST
Resume Sending
Restore company-level sending that was paused by a high permanent-bounce rate.
This is the supported remediation path, not a bypass: it never removes
suppressions and it enforces the same gates as the dashboard’s Resume sending
button.
Requires the
On success, the full sending status payload
is returned alongside these fields. On rejection, the refreshed status is nested
under
companies:manage scope plus owner or admin access to the company.
Check Get Sending Status first. For a paused
workspace, the request only restores sending when selfResume.canSelfResume is
true, which requires a high_hard_bounce_rate pause, a cleared automated
sender-health review, and no admin block. An already-active workspace succeeds
as an idempotent no-op with resumed: false. Any other blocked state needs a
support review, and the error names which gate stopped you.
On success the bounce watermark moves to now - so the rate is recalculated from
later sends - and the service attempts to requeue paused campaigns plus due
sequence steps. If part of that queue handoff is temporarily unavailable, the
request still reports the committed active state and returns recovery guidance
in message rather than falsely reporting that the resume failed. Automatic
resume is available a limited number of times before a support review is
required.
Request
boolean
required
Must be
true. Confirms the source of the invalid addresses is fixed and that
permanent bounces remain suppressed.Response fields
boolean
true when this call restored sending. false when sending was already
active.string
Sending state after the request.
active on success.string
Confirms the resume outcome. If some parked work could not be requeued, this
contains the partial-success warning and support guidance.
details.sendingStatus so the response can also describe the blocking
gate.
Responses
Resume Sending