Sign in

v101

latestOpenAPI 3.1.0raw.githubusercontent.com2026-08-08235133843.7 KB
Sending Status

Resume paused sending

Restores company-level sending paused by a high permanent-bounce rate, after the cause has been fixed. This is not a bypass - it enforces the same gates as the dashboard and never removes suppressions. For a paused workspace, sending is restored only when selfResume.canSelfResume is true on GET /sending-status, 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. On restoration the bounce watermark moves to now and the service attempts to requeue paused campaigns plus due sequence steps. A partial queue handoff still returns the committed active state with recovery guidance in message. Requires the companies:manage scope plus owner or admin access.

post/sending-status/resume

Request body

listSanitizationConfirmedboolean required

Must be true. Confirms the source of the invalid addresses is fixed and permanent bounces remain suppressed. Recorded on the account audit trail.

Response

Sending resumed, or already active

successboolean
status'active' | 'paused' | 'suspended'

Anything other than active blocks every send for this workspace, including test sends.

pauseReasonstring nullable

Enforcement message including the measured rate, the threshold it crossed, and the volume it was measured over.

pauseReasonKind'high_hard_bounce_rate' | 'high_soft_bounce_rate' | 'high_complaint_rate' | 'phishing_guard' | 'manual' | 'other' nullable

Only high_hard_bounce_rate can be cleared through the resume endpoint.

pausedAtstring date-time nullable
resumedboolean

False when sending was already active.

messagestring

Confirms the outcome, or explains that sending resumed while some parked work still needs support.

Example response

{
  "success": true,
  "pauseReason": "Bounce rate (9.910%) exceeded threshold (5%) for 111 total emails"
}