Voice and SMS APIs
Connect your own systems to your calls and texts. Click-to-dial, live call events, recordings and SMS.
The TISA APIs let your CRM, booking system or in-house tools place calls, know the moment a phone rings, pull recordings and transcripts, and send texts, all from your existing TISA account.
What you can build
The things teams usually wire up first.
- 1
Screen pops
Show the caller’s record on screen while the phone is still ringing, using the ringing event.
- 2
Click-to-dial
A Call button in your own system rings the agent’s phone, then dials the customer.
- 3
Automatic call logging
Every call, with its duration, recording and transcript, saved against the right contact.
- 4
Texts from your systems
Booking confirmations, reminders and alerts sent from your own sender name.
Voice API
Your calls, as data your systems can use.
A REST API at api.tisa.one, with JSON in and out, and webhooks that tell your server what is happening as it happens.
- Call history: inbound, outbound, internal and forwarded calls, filtered by date, direction, status or extension.
- Recordings and transcripts: a short-lived download link for each recording, and the transcript with speakers, sentiment and a summary where transcription is switched on.
- Place calls: send an extension and a number. We ring the extension, and when it answers we dial the number using that extension’s normal caller ID, recording and permissions.
- Webhooks: started, ringing, answered, ended, failed, recorded and transcribed, each signed so your server can check it came from us.
curl -X POST https://api.tisa.one/v1/calls \
-H "Authorization: Bearer tisa_live_..." \
-H "Content-Type: application/json" \
-d '{"from": "201", "to": "+447700900123"}'
SMS APIs
Texts from your systems, under your own name.
Cloud PBX SMS API
For one-to-one messages: confirmations, reminders, alerts and one-time codes. Send from your approved sender name to up to five numbers per request.
Long messages are split and joined back together on the phone, up to ten parts. Each message can be linked to an extension, so it counts towards that extension’s spend limit.
curl -X POST https://business.tisa.one/api/send-sms.php \
-H "X-API-Key: YOUR-SMS-KEY" \
-H "Content-Type: application/json" \
-d '{"sender_id": "YourBrand",
"recipients": ["07700900123"],
"message": "Your booking is confirmed."}'
Business Messaging
For campaigns and larger lists. Every TISA Business Messaging account includes API access, so you can send from your own systems as well as from the sending platform.
See SMS pricing for bundles, and the free SMS guides for what to send and when.
Built to be safe
Controls that limit what any one key can do.
- Permissions per key: a key that only reads call history cannot place calls or change webhooks.
- Lock a key to your servers: list your IP addresses and requests from anywhere else are refused, even with the right key.
- Same rules as the phone: calls placed through the API follow the extension’s permissions and spend limits.
- Numbers we never dial: emergency services, premium-rate and revenue-share numbers are refused through the API.
- Sensible limits: 60 requests a minute and 30 placed calls an hour per key. Higher limits are available on request.
- A log you can check: the last 100 requests and placed calls are listed in the portal under Call Records, API Activity.
Questions
What developers ask before they start.
What do I need to start?
A TISA Cloud PBX account. Sign in to the portal, open Voice API Keys, create a key with the permissions you need, and send it with each request. The full reference is public at business.tisa.one/developers.
Is there an extra charge for the API?
There is no separate API subscription. Calls placed through the API, texts and transcriptions are charged at your account’s normal rates, the same as if they were made from a phone or the portal.
Can a call placed through the API reach any number?
It follows the rules of the extension it comes from, so an extension set to UK only can only call UK numbers through the API too. On top of that, the API never dials emergency numbers, premium-rate numbers or revenue-share ranges such as 09, 118 and 070.
How quickly do webhooks arrive?
Ringing and answered events usually arrive within about two seconds, which is fast enough for a screen pop. Ended, recorded and transcribed events follow within about ten seconds of the information being ready.
What happens if our server is down?
We keep trying for 24 hours, waiting a little longer between each attempt, so a short outage loses nothing. Each event has an id, so your system can ignore any it has already seen.
How do we keep the key safe?
Store it on your server, never in a web page or app. Give each key only the permissions it needs, and lock it to your server’s IP addresses. Every request is listed under Call Records, API Activity, and a key can be revoked in one click.
Can we send texts and make calls with the same key?
Not yet. Voice API keys are created under Voice API Keys and SMS API keys under SMS, API Keys in the portal. Both are free to create and you can have several of each.
Next step