Calls & CDR API: Exposing Telecom Datasets
Extract historical datasets and conversational insights programmatically via ClickHouse-backed REST APIs.
Leverage our securely authenticated gateway to audit conversational assets and generate highly granular Business Intelligence (BI) dashboards. The App-Node backend exposes completely standardized RESTful OpenAPI schemas offering high-compression transmission of historical metrics, backed directly by the high-performance ClickHouse event sink.
1. The Developer Perspective: Standardization & Millisecond Latency
For IT integration teams, the CXMind REST API provides immediate access to the lowest levels of SIP signaling without the complexity of parsing PCAP files.
Retrieve Call Log Index (Paginated & Filtered)
Query the massive call_events table. Built-in multi-dimensional filtering allows frontend tables to be rendered instantly with server-side pagination.
GET /api/cdr?startDate=2026-02-01&endDate=2026-02-28&callerId=1001&limit=100&offset=0Drill-down: Full Temporal SIP Event Flow
Retrieve not just the overall duration, but the exact nanosecond timestamps of every INVITE, 200 OK, and media negotiation for a specific uuid.
GET /api/cdr/{callId}2. The Business/CRM Perspective: Data Asset Monetization
Decision-makers need macro-level visibility. CXMind breaks down the 'black box' of legacy PBX systems by exposing statistical endpoints ready to be ingested by Tableau, PowerBI, or internal CRM dashboards.
Global Platform Statistics & Conversational ROI
Extract deduplicated call volumes and aggregate event types (e.g., total abandoned vs. connected) across specific temporal boundaries, strictly isolated by tenant RBAC rules.
GET /api/cdr/stats/summary?startDate=2024-01-01&endDate=2024-01-313. The UX/Frontend Perspective: Building Fluid Interfaces
Because the API handles complex data aggregation directly within the database layer, UI developers can construct highly responsive "Search & Filter" data-grids. For example, building a "Time-Series Drag Filter" becomes trivial when the backend inherently supports startDate and endDate parameters natively mapped to ClickHouse partition keys.
Need more help or have a specific architecture question?
Contact Engineering Support