DevelopersRead only

get_transcript

API reference — one of six tools an AI assistant can call on an Avrosh account.

What it does

What was actually said on one call, in order. Only the caller and the assistant appear - internal system and tool messages are never returned. Empty when the call predates transcript linking or was never answered.

This is the exact text the model reads before deciding to call.

Parameters

business_idstringrequired

The id returned by list_businesses.

call_idstringrequired

From list_calls.

Request

curl -X POST https://us.avrosh.com/mcp \
  -H "Authorization: Bearer $AVROSH_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"get_transcript","arguments":{"business_id":"926135ac-487d-4367-8bad-25397d0d4b87","call_id":"c81f…"}}}'

Response

The result arrives as an MCP content block; the JSON below is what the text field parses to.

{
  "messages": [
    {
      "role": "guest",
      "content": "Hi, do you have anything Saturday morning?",
      "created_at": "2026-08-15T02:11:52.000Z"
    },
    {
      "role": "assistant",
      "content": "We do - 10:30 is open. Shall I hold it?",
      "created_at": "2026-08-15T02:11:56.000Z"
    }
  ]
}

Authentication

Every request carries Authorization: Bearer avk_…. Create a key in the Avrosh dashboard under Docs; it is shown once, because only its hash is stored.

One key reaches every business on the account that made it, and no others. There are no scopes to configure and nothing to switch on — a connected assistant receives the whole toolset. What bounds it is whose account the key belongs to, which is enforced in the database rather than by a permission anybody sets.

curl https://us.avrosh.com/mcp \
  -H "Authorization: Bearer $AVROSH_KEY"