List calls

Lists the calls this org has placed or received, newest first.

GET /v1/tel/calls

Addresshttps://api.hanzo.ai/v1/tel/calls
MethodGET
Operationget_tel_calls
AuthAuthorization: Bearer $HANZO_API_KEY

Lists the calls this org has placed or received, newest first. Like the message list beside it, these are our own records rather than the carrier's.

Request

GET /v1/tel/calls takes no parameters and no body — the credential is the whole request.

Response

StatusBodyMeaning
200tel.callListok
defaultproblem-detailsrefused

200 body — 7 fields.

FieldInTypeAlwaysDescription
databodytel.Call[]—Data is this org's own calls, newest first — what this platform placed or received on its behalf, which is our record rather than the carrier's.
data[].agentbodystring—Agent names the Hanzo assistant handling the call.
data[].frombodystring—From is the calling number in E.164.
data[].idbodystring—ID is the carrier's handle for the call — what a hangup or a lookup names.
data[].orgbodystring—Org is the tenant the call was placed for or received by.
data[].statusbodystring—Status is where the call is: "queued", "ringing", "answered", "completed" or "failed".
data[].tobodystring—To is the called number in E.164.

Failure carries the platform error shape — see Errors.

Examples

hanzo tel calls list
import { Configuration, TelApi } from 'hanzoai';

const api = new TelApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getTelCalls();
from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import TelApi

client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = TelApi(client).get_tel_calls()
cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.TelAPI.GetTelCalls(context.Background()).Execute()
if err != nil {
	return err
}
use hanzo_client::apis::{configuration::Configuration, tel_api};

let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();

let result = tel_api::get_tel_calls(&cfg, Default::default()).await?;
import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.TelApi;

ApiClient client = new ApiClient();
client.setBearerToken(System.getenv("HANZO_API_KEY"));

var result = new TelApi(client).getTelCalls();
curl https://api.hanzo.ai/v1/tel/calls \
  -H "Authorization: Bearer $HANZO_API_KEY"

MCP reaches tel through the tel tool, which names its 10 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:

curl -X POST https://api.hanzo.ai/v1/mcp \
  -H "Content-Type: application/json" \
  -d '{
       "jsonrpc": "2.0",
       "id": 1,
       "method": "tools/call",
       "params": {
         "name": "describe",
         "arguments": {
           "op": "list_tel_calls"
         }
       }
     }'

Tel API · All Hanzo APIs · Interactive reference

Was this page useful?