comms.get_call_transcript

Read what was said on a call, word for word — speech, not a message

Read-onlySensitiveRead budget

REST

Shipping

POST /api/v1/comms/get_call_transcript

MCP tool

Live

comms.get_call_transcript

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

Operating contract

The transcript of one call: what the caller and the shop actually said, as text. This is the SPOKEN record. comms.list_messages returns typed texts and emails; the two are different rows about different conversations and answering from the wrong one is how a shop is told a customer 'said' something they never did.

NOT EVERY CALL HAS ONE. Transcription runs on calls that reach the AI receptionist and on recorded calls long enough to be worth transcribing; a fifteen-second wrong number has audio and no words. has_transcript on comms.get_call says which before you ask.

source names what produced it, and it matters when you quote from it: a live-agent transcript is captured turn by turn during the call, an after-the-fact one is a machine transcription of the recording and carries the usual mishearings of names, plate numbers and prices. Treat a figure read out of a transcript as something to confirm, never as the price.

TIMES INSIDE A TRANSCRIPT ARE THE SHOP'S. When you summarise it back to somebody, the call's own started_at on comms.get_call is an absolute instant — render it in the SHOP's timezone rather than yours, and if you do not know the shop's timezone, ask.

This is customer speech under the same recording-disclosure regime as the audio. comms.get_call_recording says what that means; it applies verbatim to the words.

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.

Input

Field	Type	Description
callrequired	stringuuid	The call to read, as returned by comms.list_calls or comms.get_call.

Output

Field	Type	Description
call	string	—
transcript	string \| null	—
source	string \| null	—
started_at	string	—
duration_seconds	number \| 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/get_call_transcript \
  -H "Authorization: Bearer $SERVICEVIN_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"call":"…"}'

TypeScript (fetch)

const res = await fetch("https://www.servicevin.com/api/v1/comms/get_call_transcript", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.SERVICEVIN_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    "call": "…"
  }),
});

// 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/get_call_transcript",
    headers={"Authorization": f"Bearer {os.environ['SERVICEVIN_API_KEY']}"},
    json={
    "call": "…"
},
    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.get_call_transcript",
    "arguments": {
      "call": "…"
    }
  }
}

Refusals

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

Status	Code	When
404	`not_found`	The id is unknown, or the feature is not enabled for this account. Deliberately the same answer for both.
403	`forbidden`	This login does not hold calls.access.
422	`validation_error`	An argument was wrong. The message names the field.
429	`rate_limited`	Too many read calls. Back off and retry.
500	`internal_error`	Something failed on our side. Nothing was changed.

Operating contract#

Who may call it#

Input#

Output#

Examples#