Skip to main content
Documentation

Comms

comms.list_missed_calls

List missed calls and any voicemail message the caller left
Read-onlyRead budget

REST

Shipping
POST /api/v1/comms/list_missed_calls

MCP tool

Live
comms.list_missed_calls

Exposed on: REST API · Shop MCP server · Claude connector · Dash (in-app copilot) · Zapier. Part of the Comms domain.

Operating contract

The call-back list: inbound calls nobody answered, newest first, each saying whether the caller left a voicemail and how long it runs.

This is a NARROWER comms.list_calls and it exists as its own capability for the same reason Quo's own MCP server added one — 'who did we miss' is a question a shop asks by name, every morning, and making a model compose it out of two filters is how it gets composed wrong.

OUTBOUND CALLS ARE NEVER INCLUDED, whatever their status: a call the shop placed that failed to connect is a dialling problem, not somebody waiting to hear back.

has_voicemail splits the list into two different jobs. A missed call with a voicemail has a message to read first (comms.get_call_recording with kind: voicemail, or comms.get_call_transcript). A missed call without one is a cold call-back, and the customer record behind customer_id is all the context there is.

TRUNCATION: total is how many missed calls match the window and omitted how many are not in this response. When omitted is not 0, call again with offset set to next_offset.

Who may call it

Permission
calls.accessThe caller must hold Calls at the ACT level. A read-only dashboard grant on the same section is refused.
Plan
Every planNo plan gate. Available on every Service VIN plan.
Retries
naturalNaturally idempotent — running it twice leaves the same world as running it once. A retrying integration needs no key.
Rate class
readCounted against the read budget — the widest of the four.

Partial answers

omitted is how many matching records are not in the response, and 0 is a real answer meaning you have all of them. Continue with next_offset.

Do not summarise from a truncated response

When `omitted` is not 0 there are more missed calls than these. Use `total` for the count, and call again with `offset` set to `next_offset`.

Input

FieldTypeDescription
sincestringmax 40 chars

ISO instant. Only calls missed at or after it — a morning list passes midnight.

with_voicemail_onlyboolean

True to return only the missed calls that left a voicemail.

Default: false
limitinteger1–100

How many calls to return, 1-100. Defaults to 25.

Default: 25
offsetintegermin 0

How many to skip. Pass the previous response's next_offset to continue.

Default: 0

Output

FieldTypeDescription
itemsobject[]

items[].idstring

items[].conversationstring | null

items[].customer_idstring | null

items[].directionstring

items[].statusstring

items[].fromstring

items[].tostring

items[].started_atstring

items[].ended_atstring | null

items[].duration_secondsnumber | null

items[].answered_bystring | null

items[].has_recordingboolean

items[].recording_duration_secondsnumber | null

items[].has_voicemailboolean

items[].voicemail_duration_secondsnumber | null

items[].has_transcriptboolean

items[].has_ai_summaryboolean

totalnumber

omittednumber

next_offsetnumber | null

Examples

Built from this capability's own schema — required fields and the ones carrying a default, and nothing invented. Paste one and it validates.

curl
export SERVICEVIN_API_KEY=svk_live_…

curl -X POST https://www.servicevin.com/api/v1/comms/list_missed_calls \
  -H "Authorization: Bearer $SERVICEVIN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"with_voicemail_only":false,"limit":25,"offset":0}'

TypeScript (fetch)
const res = await fetch("https://www.servicevin.com/api/v1/comms/list_missed_calls", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.SERVICEVIN_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "with_voicemail_only": false,
    "limit": 25,
    "offset": 0
  }),
});

// Success and failure are both envelopes. Switch on error.code, never
// on error.message — the codes are stable, the messages are for people.
const payload = await res.json();
if (!res.ok) throw new Error(payload.error.code);
const data = payload.data;

Python (requests)
import os, requests

res = requests.post(
    "https://www.servicevin.com/api/v1/comms/list_missed_calls",
    headers={"Authorization": f"Bearer {os.environ['SERVICEVIN_API_KEY']}"},
    json={
    "with_voicemail_only": False,
    "limit": 25,
    "offset": 0
},
    timeout=30,
)
payload = res.json()
if not res.ok:
    raise RuntimeError(payload["error"]["code"])
data = payload["data"]

MCP tools/call — https://www.servicevin.com/api/mcp
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "comms.list_missed_calls",
    "arguments": {
      "with_voicemail_only": false,
      "limit": 25,
      "offset": 0
    }
  }
}

Refusals

The four gates run in this order on every surface, and the order is not arbitrary — see Authentication.

StatusCodeWhen
404not_foundThe id is unknown, or the feature is not enabled for this account. Deliberately the same answer for both.
403forbiddenThis login does not hold calls.access.
422validation_errorAn argument was wrong. The message names the field.
429rate_limitedToo many read calls. Back off and retry.
500internal_errorSomething failed on our side. Nothing was changed.