Live call concurrency
How many voice calls your workspace has up right now, and the ceiling the admission gate refuses at. Added on 2026-09-15.
active is the live counter the admission gate itself reads, so the number here and the number that
decides whether your next POST /api/calls connects can never disagree. max is the effective
ceiling: the lower of the platform ceiling and your plan’s concurrency limit, because that is the
value a caller is actually refused at — not the plan limit on its own.
The workspace is taken from the credential. There is no tenant parameter, and one workspace cannot read another’s.
GET /health never carried this: it is a platform probe with no workspace, so anything reading
activeCalls from it was reading a number that did not exist. Use this route instead.
Consistency. Not cached; each call reads the live counter.
Idempotency. Read-only; safe to retry.
Access
- Required scope:
read(orwrite). - Rate limit: General API — 120 (Starter), 200 (Growth), 300 (Business) or 600 (Enterprise) requests/min per workspace. The 20/min outbound limit does not apply to this route. See Rate limits.
- Plan: Available on every plan. It is deliberately not behind the live-monitor feature, because every workspace is entitled to read its own capacity.
Authentication
Workspace API key: jl_ followed by 64 lowercase hex characters, created by the workspace owner in the
dashboard (Settings → API Keys) and sent as Authorization: Bearer jl_.... The plaintext is shown once,
at creation; Jelliu stores only a SHA-256 hash. A workspace can hold up to 25 active keys.
Operations restricted to admins or owners reject keys without the full scope with 403, and say so in
their description. No key, whatever its scope, can mint or revoke API keys or rotate a webhook secret —
that requires a signed-in owner session. A revoked key stops authenticating within about 10 seconds.
See Authentication.