Changelog

Added

Typing indicators

Set a typing indicator — POST /api/v1/typing with {toNumber, value, fromNumber} shows (or clears) a typing indicator on the recipient’s device, as if someone were composing from your number. iMessage numbers display it; standard (SMS) numbers have no typing concept and silently no-op, so you can call it unconditionally before a send. Delivering a message or reaction from the same number clears the indicator natively — start again after a send if you’re still composing. Free of charge.

Available everywhere: dial typing start / dial typing stop in the CLI, startTyping / stopTyping primitives plus a scoped typing() session (starts on creation, stops on dispose, prefills sends) in the Node and Python SDKs, a typing tool in the agent SDKs, and on the MCP server.

Zapier integration

The Dial app for Zapier connects Dial to 7,000+ apps — trigger Zaps from inbound messages and completed calls, and send messages or place calls as Zap actions. No code required.

Changed

Flexible from-number references

sendMessage, makeCall, and sendTyping now accept fromNumber — a phone-number ID, one of your numbers in E.164 format, or a number’s nickname — instead of requiring the raw ID. An ambiguous nickname is rejected with 400; a ref matching none of your numbers returns 404. fromNumberId remains as the id-only alternative; pass exactly one of the two.