API referenceGet call analytics

Calls

Get call analytics

Compute aggregate analytics over historical calls that match a filter. Accepts the same SearchCallsRequest body as the search endpoint, but instead of returning individual call rows it returns summarized analytics for the matching set (counts, durations, status breakdowns, and similar metrics). Use it to power dashboards and reporting over a date range, agent, status, or tag rather than to page through raw calls.

POST

https://api.nabrah.ai/api/ext/call/analytics

Get call analytics

curl --request POST \
  --url 'https://api.nabrah.ai/api/ext/call/analytics' \
  --header 'X-API-Key: <your-api-key>' \
  --header 'Content-Type: application/json' \
  --data '{
  "created_at_start": "2026-06-01T00:00:00.000Z",
  "created_at_end": "2026-06-23T23:59:59.000Z"
}'

// No example body for this response.

Filtering

Send only the fields you want to constrain on; omit the rest. All filters are combined (AND). Same body as POST /api/ext/call/search.

Time windows

call_started_at_start / call_started_at_end filter by when the call actually started; created_at_start / created_at_end filter by when the record was created. Use ISO-8601 timestamps.

call_started_at_startcall_started_at_endcreated_at_startcreated_at_end

Scope by agent / number / status

agent_id restricts to one agent; call_from and call_to filter by phone number; status filters by lifecycle state (queued, ringing, in-progress, completed, failed); call_type filters inbound vs outbound.

agent_idcall_fromcall_tostatuscall_type

Tags and free text

tags matches calls carrying any of the listed tags; tag is a single-tag convenience filter; q is a free-text search across call content.

tagstagq

Analysis filters

analysis_filters constrains by post-call analysis values. Each entry is { name, op, value } where op is a comparison operator such as ==, !=, >, <.

nameopvalue

limit and offset are accepted for parity with search but have no effect on aggregate totals; analytics are computed over the entire matching set.

Getting an agent_id

To filter by agent, fetch the project's agents first.

GET /api/ext/agent

Lists the agents in your project; use an agent's id as agent_id here.

Authorization

X-API-Keystringheaderrequired

Your workspace API key. Create one in the dashboard under API keys.

Body

application/json

Analytics over a date range with no other constraints.

Minimal

{
  "created_at_start": "2026-06-01T00:00:00.000Z",
  "created_at_end": "2026-06-23T23:59:59.000Z"
}

Response

200

Successful Response

application/json

422

Validation Error

application/json

API referenceGet call analytics

Calls

Get call analytics

POST

https://api.nabrah.ai/api/ext/call/analytics

Get call analytics

curl --request POST \
  --url 'https://api.nabrah.ai/api/ext/call/analytics' \
  --header 'X-API-Key: <your-api-key>' \
  --header 'Content-Type: application/json' \
  --data '{
  "created_at_start": "2026-06-01T00:00:00.000Z",
  "created_at_end": "2026-06-23T23:59:59.000Z"
}'

// No example body for this response.

Filtering

Send only the fields you want to constrain on; omit the rest. All filters are combined (AND). Same body as POST /api/ext/call/search.

Time windows

call_started_at_start / call_started_at_end filter by when the call actually started; created_at_start / created_at_end filter by when the record was created. Use ISO-8601 timestamps.

call_started_at_startcall_started_at_endcreated_at_startcreated_at_end

Scope by agent / number / status

agent_idcall_fromcall_tostatuscall_type

Tags and free text

tags matches calls carrying any of the listed tags; tag is a single-tag convenience filter; q is a free-text search across call content.

tagstagq

Analysis filters

analysis_filters constrains by post-call analysis values. Each entry is { name, op, value } where op is a comparison operator such as ==, !=, >, <.

nameopvalue

limit and offset are accepted for parity with search but have no effect on aggregate totals; analytics are computed over the entire matching set.

Getting an agent_id

To filter by agent, fetch the project's agents first.

GET /api/ext/agent

Lists the agents in your project; use an agent's id as agent_id here.

Authorization

X-API-Keystringheaderrequired

Your workspace API key. Create one in the dashboard under API keys.

Body

application/json

Analytics over a date range with no other constraints.

Minimal

{
  "created_at_start": "2026-06-01T00:00:00.000Z",
  "created_at_end": "2026-06-23T23:59:59.000Z"
}

Response

200

Successful Response

application/json

422

Validation Error

application/json