Skip to main content
GET
Campaign capacity and monitoring
Use the account capacity endpoint before and during a campaign to understand how many calls can run concurrently.
account_id
string
required
Your Vobiz account ID. Use the same value in X-Auth-ID.
X-Auth-ID
string
required
Your Vobiz account ID, for example MA_XXXXXXXX.
cURL
The response includes:
  • concurrent_calls — active calls across the account.
  • max_concurrent — account concurrency limit.
  • concurrent_free — capacity available for new calls.
  • utilization_pct — current utilization percentage.
  • running_campaigns — summaries of campaigns consuming capacity.
The endpoint returns 502 when the upstream platform concurrency service is unavailable.

Capacity behavior

max_concurrent on a campaign cannot exceed the account concurrency limit. Capacity is enforced at dial time. A saturated account does not fail the campaign; the campaign remains running and waits until a slot becomes available.
The cps field remains for backward compatibility, but it does not gate campaign capacity. Use live concurrency and max_concurrent when reasoning about throughput.

Monitoring endpoints

Health and automatic pauses

A running campaign reports active, idle, stalled, or not_started health. Operational pause reasons include:
  • manual_pause
  • window_closed
  • caller_pool_exhausted
  • caller_pool_daily_limit_reached
  • account_inactive
  • stalled
  • consecutive_failures
  • balance_insufficient
Some reasons require manual action. Daily window and pool daily-limit pauses can resume automatically at the appropriate time.