Statistics API and AI
Read-only by designThe same statistics as the JEDWare reports, outside the app: pulled into your BI tools through the API, or answered in plain language by your AI assistant.
14 days free ยท full access ยท no credit card
Sample conversation. Claude, ChatGPT and other assistants through MCP.
The problem
Power BI wants a data source, the warehouse wants a nightly sync, and the manager wants to ask a question in a chat window. Screenshots and CSV exports do not scale.
Why teams love it
The Statistics API returns the same numbers as the JEDWare reports, computed by the same reporting service, so what lands in Power BI always matches what the app shows.
Agents, queues, ring groups, departments, agent status, queue availability, callbacks, calls and talk time, as JSON.
Every endpoint is plain HTTP POST with a JSON body, documented on your own system with pre-filled examples you can run in the browser.
Through MCP your assistant connects straight to your own 3CX and answers questions instead of you writing API requests.
A key is shown once, stored hashed, works within seconds and can be revoked at any time. Revoked keys stay in the list as history.
What's inside
MCP is an open standard supported by Claude, ChatGPT, Microsoft Copilot, Cursor and most other AI tools. JEDWare adds no AI of its own: the data flows between your server and your AI provider, and JEDWare never sees the conversation.
Ask about "the support queue" and plain-language periods like yesterday, last week or last 30 days.
The assistant chooses the report, fills in dates and filters, and summarizes the result.
Live Chat, WhatsApp, Facebook and SMS statistics answer the same way as calls.
"How many calls did queue 800 answer yesterday, and how many were lost?" "Show answered percentage per queue for last month." "Which agent had the most WhatsApp chats last week?"
Statistics come out, nothing gets changed. Not through the API, not through an assistant.
Claude Desktop, claude.ai, ChatGPT, Cursor and any other MCP client. Setup is described per client in the knowledge base.
API keys
Access runs on API keys your administrators manage in the app. One key per tool: powerbi, warehouse-sync, claude. One integration can be cut off without touching the others.
Pricing
Read-only by designThe Statistics API and the MCP connection come with the app. Requires a JEDWare integration updated in September 2026 or later. Full access for 14 days, no credit card.
Requires 3CX v20 Update 6 or later, Linux or Windows.
The JEDWare Statistics API exposes nine report endpoints as plain HTTP POST with a JSON body: agents, queues, ring groups, departments, agent status, queue availability, callbacks, calls and talk time. They are computed by the same reporting service as the app, so Power BI, Excel or your warehouse always match what the reports show.
Interactive Swagger documentation runs on your own system with pre-filled examples, and the OpenAPI file imports into Postman, Insomnia and code generators.
Through MCP, an open standard supported by Claude, ChatGPT, Microsoft Copilot, Cursor and most other AI tools, your assistant connects to your own 3CX data and answers questions in plain language. JEDWare adds no AI of its own and never sees the conversation.
Access runs on API keys created and revoked in the app by your administrators, shown once and stored hashed. Everything is read-only. See pricing for what is included.
Ready when you are
Free for 14 days with your own 3CX data. Full access, no credit card.
