Pause Account Sending
Stop campaign email from one account without disconnecting it.
https://api.foxreach.io/ api/ v1/ email-accounts/{account_id}/ pauseRequires an API key with the write scope.
Stops campaign email from this account. Sends already queued on it are released and go out from the campaign's other accounts on the next scheduling pass; a follow-up whose own account is paused goes out from another account in the campaign. Replies keep arriving in the inbox, you can still reply by hand from the account, and warmup carries on. Pausing an account that is already paused changes nothing. Each pause is recorded in the Audit Log with who paused it and the reason. Resume with Resume Account Sending.
Path Parameters
account_id string path required The unique identifier of the email account.
Body
reason string body Optional note on why sending is paused, up to 200 characters. Shown in the audit log.
Response
data object The email account object. Passwords and OAuth tokens are never returned.
data
id string email string displayName string null.provider string smtpHost string smtpPort integer imapHost string imapPort integer timezone string dailyLimit integer sentToday integer warmupEnabled boolean warmupDailyLimit integer warmupRampUpDays integer warmupStartDate string null.healthScore integer null. For the live placement score use Get Account Health.domainAuth object null until checked.domainAuthCheckedAt string null.bounceRate number replyRate number isActive boolean connectionStatus string connected.lastError string null.sendingPausedAt string null while the account sends.sendingPausedReason string null.createdAt string updatedAt string Errors
| Status | Description |
|---|---|
401 | Missing, invalid, revoked or expired API key |
403 | API key does not have the required scope: write |
404 | Email account not found, or it belongs to another workspace |
422 | reason is longer than 200 characters |
Rate Limit
- 120 requests per minute, shared by every
writecall in your workspace. Fixed 60-second window. - Every response includes
X-RateLimit-Limit,X-RateLimit-Remaining,X-RateLimit-Reset(unix epoch seconds) andX-RateLimit-Bucket(write). - A
429response includes aRetry-Afterheader (seconds until the bucket resets).
For client-side patterns (Retry-After, exponential backoff, monitoring X-RateLimit-Remaining), see Rate Limiting.