Twilio: 3 reads and 3 writes, one client
Send SMS & browse messages with your own Account SID + token. Every call below is available over HTTP, through the SDK and as a tool for a coding agent, with the same arguments and the same meter.
What Twilio can do here
The integration exposes 3 reads and 3 writes, each with a declared input and output schema rather than a page of documentation you would have to translate. Send SMS & browse messages with your own Account SID + token.
How it authenticates
Twilio authenticates with a authToken, supplied per request or stored once against your account and sealed at rest. On our side the same value is read from accountSid and authToken when we broker the call for you.
Capabilities it fulfils
Twilio answers sms.list, sms.send and voice.call.create in the vendor-neutral form, which means code asking for any of those can be pointed at Twilio without naming it. If it goes down, or you would rather use somebody else, that is a preference change and not a rewrite.
- sendSms — write: Send an SMS.
- listMessages — read: List messages.
- createCall — write: 🔴 PLACES A REAL PHONE CALL AND SPENDS REAL MONEY. It rings a real person, cannot be un-rung, and is billed per minute from the moment it connects. Never wire it to an automatic trigger without a human step.
- listCalls — read: List calls.
- getCall — read: One call — the way to learn what actually happened after createCall returned queued.
- endCall — write: 🔴 HANGS UP A CALL IN PROGRESS. Send Status=completed. There is no undo and the far end simply hears the line drop.
Questions
Do I have to bring my own API keys?
You can, and that lane is free for ever — pass your key on the request or store it against your account, and we are one proxy hop. The paid lane is the other direction: we call 226 providers with our credentials so you never register anywhere. Both go through the same client and the same operation names.
What happens to a key I store here?
It is sealed with AES-256-GCM before it reaches the database and is only ever opened to make the call you asked for. It is scoped to your account, it is never logged, and deleting the connection deletes it. For an OAuth provider we hold a refresh token instead, and revoking the link at the provider stops the calls here immediately.
What happens when a provider changes its API?
The operation contract is declared, so a response that no longer matches is a refusal rather than a silently wrong answer. The contract does not coerce types — a field declared a number that arrives as a string is rejected at the edge, on the way in and on the way out.