Per-Account Sending Limits

MigoSMTP applies sending limits at the workspace level — not per individual SMTP account. This means all SMTP accounts on your workspace share a common pool of monthly quota and daily/hourly limits. Understanding how this shared model works helps you plan your usage across multiple accounts and integrations without hitting unexpected blocks.

How Limits Are Shared Across Accounts

Viewing Usage Per SMTP Account

While limits are workspace-wide, usage attribution is tracked per account — so you can see exactly which account is consuming your quota:

1. Go to MigoSMTP → SMTP Accounts.
2. The accounts list shows Sent this month for each account.
3. Click any account to open the detail view showing:
   • Total sent all-time
   • Sent this month (contribution to workspace quota)
   • Delivery rate for this account
   • Last used timestamp
4. Sum all accounts' monthly usage to see total workspace consumption versus your plan quota.

Monitoring Combined Usage via the API

// Get workspace-level usage (all accounts combined)
GET https://api.migosmtp.com/v1/account/usage
Authorization: Bearer YOUR_API_KEY

// Response includes combined totals:
{
  "monthly_quota":     30000,
  "monthly_used":      18450,   // All accounts combined
  "daily_limit":       1500,
  "daily_used":        342,
  "hourly_limit":      150,
  "hourly_used":       23,
  "by_smtp_account": [
    { "account_id": "acc_abc", "name": "Production", "monthly_used": 16200 },
    { "account_id": "acc_def", "name": "Staging",    "monthly_used": 2250  }
  ]
}

Strategies for Managing Shared Limits

Strategy 1 — Prioritise Transactional Over Marketing

Configure your bulk marketing sends to check remaining quota before submitting large batches:

// Before any bulk marketing send, verify enough capacity exists
async function checkCapacityForBulkSend(recipientCount) {
  const usage = await getWorkspaceUsage();
  const safeBuffer = 500; // Reserve 500 emails for transactional

  const available = Math.max(0,
    usage.daily_remaining - safeBuffer
  );

  if (available < recipientCount) {
    // Schedule for next day instead
    return {
      canSendNow: false,
      available,
      scheduleFor: usage.daily_reset_at
    };
  }
  return { canSendNow: true, available };
}

Strategy 2 — Separate Workspaces for High-Volume Mixed Sending

If you send both high-volume marketing email AND time-critical transactional email, the most reliable approach is to have separate MigoSMTP subscriptions:

• Workspace A — Transactional-only subscription (lower plan is fine — OTPs and password resets have low volume)
• Workspace B — Marketing/bulk subscription (higher plan for volume capacity)

This completely eliminates the risk of marketing sends consuming capacity needed for transactional delivery.

Strategy 3 — Schedule Marketing Sends Off-Peak

If using a single workspace, schedule marketing bulk sends overnight (11 PM – 5 AM IST) when transactional volume is low. This ensures the daily limit is fresh for peak transactional hours (9 AM – 9 PM).

Per-Account Limits — What Is Configurable

Next Steps

• Understanding sending limits & quotas
• Managing multiple SMTP accounts
• How throttling works