Error responses
| Status | Meaning | Typical cause |
|---|---|---|
400 Bad Request | Invalid input; the response body says what | end before start, unknown extension/ring group, invalid time zone, slaSeconds of 0, invalid interval |
401 Unauthorized | Missing, wrong or revoked API key | Check the X-Api-Key header and the key’s status in the JEDWare app |
404 Not Found | Group not found | The groupId doesn’t exist or the group has no members |
503 Service Unavailable | The integration could not resolve its configuration | Temporary. Retry, and contact support if it persists |
Why is a number lower than I expected?
Queue statistics count queue calls only. A call that rings an extension directly (or via a ring group) never appears in queue statistics. Use /agents, /ringgroups or /calls for those. If a number looks lower than expected, check /calls for the same period to see where the calls actually landed.
Agent statistics count participation. An agent row includes calls the agent took part in anywhere in the call’s path, matching the JEDWare app’s agent report.
Good to know
- SLA columns in queue and ring group responses may currently show 0. An update to the reporting backend is in progress. All other columns are unaffected.
- Statistics are computed from the JEDWare reporting service, the same source as your scheduled PDF/CSV reports, so numbers always match your JEDWare reports.
- Lost your key? Support cannot recover it, by design. JEDWare never stores the key itself, only a cryptographic hash of it. Revoke the lost key and generate a new one; the swap takes under a minute.