List messages

Lists the messages this org has sent or received, newest first.

GET /v1/tel/messages

Tel → · All API references → · Get started →

Address	`https://api.hanzo.ai/v1/tel/messages`
Method	`GET`
Operation	`get_tel_messages`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Lists the messages this org has sent or received, newest first. Records from our own store, not the carrier's — so it is what this platform did on the org's behalf, which is the set an audit or a bill has to agree with.

Request

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

Response

Status	Body	Meaning
`200`	tel.messageList	ok
`default`	problem-details	refused

200 body — 7 fields.

Field	In	Type	Always	Description
`data`	body	tel.SMS[]	—	Data is this org's own messages, newest first — from our store rather than the carrier's, so it is the set an audit or a bill has to agree with.
`data[].from`	body	string	—	From is the sending number in E.164, and must be one this org holds.
`data[].id`	body	string	—	ID is the carrier's handle for the message.
`data[].org`	body	string	—	Org is the tenant the message was sent for or received by.
`data[].status`	body	string	—	Status is where the message is: "queued", "sent", "delivered" or "failed".
`data[].text`	body	string	—	Text is the message body.
`data[].to`	body	string	—	To is the receiving number in E.164.

Failure carries the platform error shape — see Errors.

Examples

CLI

SDK

HTTP

MCP

hanzo tel messages get

.ts

.py

.go

.rs

.java

import { Configuration, TelApi } from 'hanzoai';

const api = new TelApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getTelMessages();

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_messages()

cfg := hanzoai.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := hanzoai.NewAPIClient(cfg)

resp, _, err := client.TelAPI.GetTelMessages(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_messages(&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).getTelMessages();

curl https://api.hanzo.ai/v1/tel/messages \
  -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?

PreviousList calls NextList available