AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Vobiz Cdr

skill-vobiz-ai-agent-skills-vobiz-cdr · by vobiz-ai

Query Vobiz Call Detail Records - list, search, retrieve by call_id, fetch recent, and export CSV. 43 fields per CDR including quality metrics (MOS, jitter, packet loss) and hangup attribution.

No reviews yet
0 installs
27 views
0.0% view→install

Install

$ agentstack add skill-vobiz-ai-agent-skills-vobiz-cdr

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access Used
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-vobiz-ai-agent-skills-vobiz-cdr)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Vobiz Cdr? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Vobiz CDR skill

Use this for call history, billing reconciliation, quality analysis, or analytics. A CDR is written after a call completes - it is not available mid-call. Poll the list/recent endpoints, or use trunk webhooks for real-time events.

Base URL: https://api.vobiz.ai. Auth headers on every request: X-Auth-ID and X-Auth-Token.

Endpoints

| Op | Path | Notes | |---|---|---| | List | GET /api/v1/Account/{auth_id}/cdr | Filter by from/to number, date range, direction, min_duration; paginated; includes summary | | Search | GET /api/v1/Account/{auth_id}/cdr/search | Same filters + adds a filters echo of the active filter values | | Recent | GET /api/v1/Account/{auth_id}/cdr/recent | Last 20 by default (limit to change). No pagination, no summary, no filters | | Export | GET /api/v1/Account/{auth_id}/cdr/export | Returns text/csv, not JSON. Same filters as list (no page/per_page) | | Get one | GET /api/v1/Account/{auth_id}/cdr/{call_id} | Path param is named call_id; pass the call's uuid from a list/webhook |

auth_id is your master account ID (MA_XXXXXXXX). The path segment is Account (capital A) followed by lowercase cdr - match the casing exactly.

Response shape

Top-level (list): { account_id, count, data, pagination, summary, success }. Search adds filters. Recent returns only { account_id, count, data, success }. Get-one returns { data, success } where data is a single object (not an array).

pagination: { page, per_page, total, pages, has_next, has_prev } (NOT current_page / total_records). total is the count across all pages; pages = ceil(total / per_page).

summary: { totalCalls, answeredCalls, answerRate, avgCallDuration, total_duration_seconds, total_billable_seconds, total_cost, last_call_at }. Note avgCallDuration is a string like "28s", not a number. The summary reflects the filtered set, not the whole account.

filters (search only): { call_direction, from_number, hangup_cause, to_number }. Empty values come back as "", not omitted.

Each CDR object has 43 fields. See the field glossary below.

Filters that work

Apply to list, search, and export (export ignores page/per_page):

  • from_number - originating number; substring or full E.164 (example value 9876543210)
  • to_number - destination number; substring or full E.164
  • start_date - YYYY-MM-DD. Required together with end_date
  • end_date - YYYY-MM-DD. Required together with start_date
  • call_direction - enum: inbound or outbound (no other values)
  • min_duration - integer seconds; excludes calls shorter than this
  • page - default 1 (list, search only)
  • per_page - default 20, max 100 (list, search only)

Recent takes only limit (default 20).

Field glossary (CDR object)

Identity & routing: id (integer, internal), uuid (string, globally unique - use this for get-one), account_id, call_direction (inbound/outbound), caller_id_name, caller_id_number (E.164, NOT from_number), destination_number (NOT to_number), context, region, origination_region, campaign_id (nullable), customer_endpoint (nullable), trunk_id (nullable), terminated_to (nullable).

Timing & duration: duration (integer seconds, ring + talk), billsec (integer billable seconds, talk only), ring_time, answer_time (nullable - null if unanswered), start_time, end_time, progress_time, created_at, updated_at. Timestamps are ISO 8601 (...Z).

Billing: cost, total_cost (cost + streaming), streaming_cost, currency (e.g. INR).

Quality metrics: mos (1.0-5.0, higher is better; 0 on unanswered/failed), jitter (ms), packet_loss (%), codec (PCMU/PCMA/opus, nullable). All quality fields are nullable and may be 0 for calls that never carried media.

Hangup attribution: hangup_cause (string, e.g. NORMAL_CLEARING), hangup_cause_code (integer, e.g. 4000), hangup_cause_name (e.g. Normal Hangup), hangup_disposition (send_bye/recv_bye/send_cancel...), hangup_source (Caller/Callee/Carrier/...), failure_code (nullable), failure_reason (nullable).

SIP / network: bridge_uuid (nullable), sip_call_id, sip_user_agent (nullable), network_addr (nullable), carrier_ip (nullable).

Recipes

List a date range, page 2, 50/page:

curl -G "https://api.vobiz.ai/api/v1/Account/$AUTH_ID/cdr" \
  --data-urlencode "start_date=2026-03-01" \
  --data-urlencode "end_date=2026-03-17" \
  --data-urlencode "page=2" --data-urlencode "per_page=50" \
  -H "X-Auth-ID: $AUTH_ID" -H "X-Auth-Token: $AUTH_TOKEN"

Search outbound calls from one number, echo the filters:

curl -G "https://api.vobiz.ai/api/v1/Account/$AUTH_ID/cdr/search" \
  --data-urlencode "call_direction=outbound" \
  --data-urlencode "from_number=919876543210" \
  -H "X-Auth-ID: $AUTH_ID" -H "X-Auth-Token: $AUTH_TOKEN"

Export filtered CDRs to a CSV file (no Accept: application/json):

curl -G "https://api.vobiz.ai/api/v1/Account/$AUTH_ID/cdr/export" \
  --data-urlencode "start_date=2026-03-01" --data-urlencode "end_date=2026-03-17" \
  -H "X-Auth-ID: $AUTH_ID" -H "X-Auth-Token: $AUTH_TOKEN" \
  -o cdrs.csv

Walk every page until has_next is false (jq):

page=1
while :; do
  resp=$(curl -sG "https://api.vobiz.ai/api/v1/Account/$AUTH_ID/cdr" \
    --data-urlencode "page=$page" --data-urlencode "per_page=100" \
    -H "X-Auth-ID: $AUTH_ID" -H "X-Auth-Token: $AUTH_TOKEN")
  echo "$resp" | jq -c '.data[]'
  [ "$(echo "$resp" | jq '.pagination.has_next')" = "true" ] || break
  page=$((page+1))
done

Get a single CDR by its uuid (taken from data[].uuid):

curl "https://api.vobiz.ai/api/v1/Account/$AUTH_ID/cdr/$CALL_UUID" \
  -H "X-Auth-ID: $AUTH_ID" -H "X-Auth-Token: $AUTH_TOKEN"

Pitfalls

  • Casing: the path is /api/v1/Account/{auth_id}/cdr - Account is capitalized, cdr is lowercase. Lowercasing Account or capitalizing cdr will 404/401.
  • get-cdr uses the uuid, not the numeric id: the path param is named call_id, but pass the call's uuid (from data[].uuid or a webhook). Feeding back the numeric data[].id returns 404.
  • Export is not JSON: the export endpoint returns text/csv. Don't send Accept: application/json; pipe to a file with curl -o cdrs.csv. page/per_page are ignored - filter with start_date/end_date/min_duration to limit rows.
  • Date filters are paired: start_date and end_date must be supplied together, both YYYY-MM-DD. A lone date may be ignored.
  • Field name drift: it's caller_id_number/destination_number on the CDR object, but the filter params are from_number/to_number. Don't filter on caller_id_number.
  • avgCallDuration is a string ("28s") - parse it, don't do math on it directly. For numeric aggregates use total_duration_seconds / total_billable_seconds.
  • Recent has no pagination or summary: only account_id, count, data, success. Use list if you need totals or paging.
  • Empty result set: a valid request that matches nothing returns 200 with data: [], count: 0, and a zeroed summary (not a 404).
  • Quality fields can be 0 or null on unanswered/failed calls - treat mos: 0 as "no media", not "worst quality".
  • Hangup causes: the full numeric-code reference (4000, 1010, 2030, 3130, etc.) and the textual SIP causes live in the canonical [Hangup Causes](/concepts/hangup-causes) page. The CDR overview at /cdr.mdx also carries the textual hangup_cause table.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.