Skip to main content
@telzino/server sends texts and places outbound calls with a Telzino API key. It runs on your server (Node.js 18 or later). Never ship it, or the key, to a browser: for the browser use chat and voice with a publishable key.
The SDK gets an access token with the client credentials flow, keeps it until shortly before it expires, and gets a new one if the key’s secret was rotated. Every request gives up after 30 seconds.

Send a text

The text goes out from the agent’s SMS number and joins that customer’s conversation. When the customer replies, the agent answers. See Send SMS for the rules: the agent needs an enabled SMS number, and recipients who texted STOP are refused.

Place an outbound call

callbackUrl and metadata are supported too. Any other field of Trigger Outbound Call goes in extra, in the API’s snake_case, for example extra: { retry_policy_id: '...' }.

Which key to use

Create the key in the dashboard under API Keys. For a backend that only texts and calls for one agent, choose Access → One agent: that key can send that agent’s texts and place its calls, and nothing else. See Agent-scoped API keys.

Errors

Failures throw a TelzinoApiError with the HTTP status and the API’s code:
Common codes: opted_out, sms_not_enabled, rate_limited, not_found, insufficient_scope, invalid_request.