Skip to content
Compliance included · one account for numbers, voice and SMS · 191 countries covered.Compliance included · one account for numbers, voice and SMS · 191 countries covered.Compliance included · one account for numbers, voice and SMS · 191 countries covered.Compliance included · one account for numbers, voice and SMS · 191 countries covered.
Twiching
API Reference

Build anything. Ship it today.

REST API for voice, SMS, number management, webhooks, and analytics. Bearer token auth. Versioned, documented, and available in 5 SDKs.

API
api.twiching.ai
REST · v1
live
Request stream
POST
/v1/calls
142ms200
POST
/v1/messages
88ms
GET
/v1/calls/{id}
54ms
POST
/v1/webhooks
203ms
GET
/v1/analytics/calls
67ms
99.99%
Uptime
88ms
p50
3
Regions
How it works

One base URL. Four rules.

Every endpoint below follows the same pattern, so once your first request works the rest do too.

01

Base URL

Every request goes to https://api.twiching.ai/v1/ over HTTPS. Plain HTTP is rejected.

02

Authenticate

Send your API key as a Bearer token, or fetch a short-lived token with OAuth 2.0.

03

Send JSON

Request bodies are JSON. A successful request returns a 200 or 201 status.

04

Test first

The sandbox at sandbox.twiching.ai/v1/ never reaches real numbers and is free.

Endpoints

Core REST surface

Base URL: https://api.twiching.ai

Voice

Place calls and look up what happened on them. Covers PSTN calling, SIP trunking, call control and recording.

POST/v1/calls
GET/v1/calls/{id}

Messaging

Send an SMS or MMS and look it up later. Long code, short code and toll-free numbers are supported.

POST/v1/messages
GET/v1/messages/{id}

Numbers

Find a number, then provision it. Numbers are available in 191 countries from the same API.

POST/v1/numbers/search
POST/v1/numbers/provision

Analytics

Pull a summary of your call analytics without opening the dashboard.

GET/v1/analytics/calls

Webhooks

Register a URL and Twiching sends it events as they happen. Payloads are signed with HMAC-SHA256.

POST/v1/webhooks
Common flows

Three calls that do the job.

Most integrations are a short chain of requests. These are the three we see most.

Call and follow up

  1. 01POST /v1/calls to start the call.
  2. 02POST /v1/webhooks to subscribe to call.completed.
  3. 03GET /v1/calls/{id} to read the details when it ends.

Send and confirm

  1. 01POST /v1/messages to send an SMS or MMS.
  2. 02POST /v1/webhooks to subscribe to message.delivered.
  3. 03GET /v1/messages/{id} to check one message later.

Get a number and use it

  1. 01POST /v1/numbers/search to find an available number.
  2. 02POST /v1/numbers/provision to claim it.
  3. 03Use it as the from number when you start a call.
Authentication

Two ways to authenticate.

Bearer token

Bearer token

Pass your API key in the Authorization header on every request.

Authorization: Bearer sk_live_•••••••
OAuth 2.0

OAuth 2.0

Use client credentials flow for machine-to-machine integrations.

POST /oauth/token → access_token
Example

Place your first call.

Send a POST to /v1/calls with the number to dial and the number to dial from. The response carries the call id.

Keep that id. Request GET /v1/calls/{id} later to see how the call went, or subscribe to webhook events and let Twiching tell you.

Request
POST https://api.twiching.ai/v1/calls
Authorization: Bearer tw_live_xxxxxxxxxxxxxxxx
Content-Type: application/json

{
  "to":   "+14155551234",
  "from": "+12125550001"
}
Response (shortened)
HTTP/1.1 200 OK

{
  "sid": "CA1a2b3c4d…",
  "status": "initiated"
}
Webhooks

Events you can subscribe to.

Register a URL with POST /v1/webhooks and pick the events you want. Signing, retries and delivery are covered on the docs page.

Calls

call.initiatedcall.ringingcall.answeredcall.completedcall.failed

Messages

message.sentmessage.deliveredmessage.failed

Recordings

recording.ready
SDKs

Your language. Your stack.

Every SDK wraps the same endpoints, so the requests on this page translate directly into your language.

Node.js

npm install

Python

pip install

Go

go get

Ruby

gem install

PHP

composer require
What businesses say

What Our
Customers Says

Reliable communication built for modern teams. From clinics to real-estate offices, businesses stay reachable without missed calls, disconnected systems, or outdated phone setups.

Contact Us
MW

Marcus Whitfield

Broker · Arbor Homes Realty

“Every listing city has its own local number now. Open-house calls actually get answered — no more screened voicemails from unknown prefixes.”
EC

Dr. Elaine Carter

Director · Northside Family Clinic

“Moved our appointment reminders and after-hours line in a weekend. Patients don't hit voicemail at 5:01 PM anymore, and the whole thing stayed HIPAA-aligned.”
DH

Devon Harper

Co-founder · Telemetry SaaS

“Our support number used to show as “unknown caller” in customers’ CRMs. Not anymore. One account, one bill, one team that picks up.”
SB

Sophia Bennett

Operations · Beacon Logistics

“Porting our business numbers was smoother than expected. The onboarding team handled everything while we stayed live.”
NR

Noah Richardson

Marketing Lead · Elevate Media

“The analytics dashboard finally shows which campaigns drive actual phone calls. Our ad spend makes sense now.”
MW

Marcus Whitfield

Broker · Arbor Homes Realty

“Every listing city has its own local number now. Open-house calls actually get answered — no more screened voicemails from unknown prefixes.”
EC

Dr. Elaine Carter

Director · Northside Family Clinic

“Moved our appointment reminders and after-hours line in a weekend. Patients don't hit voicemail at 5:01 PM anymore, and the whole thing stayed HIPAA-aligned.”
DH

Devon Harper

Co-founder · Telemetry SaaS

“Our support number used to show as “unknown caller” in customers’ CRMs. Not anymore. One account, one bill, one team that picks up.”
SB

Sophia Bennett

Operations · Beacon Logistics

“Porting our business numbers was smoother than expected. The onboarding team handled everything while we stayed live.”
NR

Noah Richardson

Marketing Lead · Elevate Media

“The analytics dashboard finally shows which campaigns drive actual phone calls. Our ad spend makes sense now.”

FAQ

Questions about the Twiching API, answered.

Voice calls, SMS and MMS messages, phone numbers, call analytics and webhooks. Each one has its own endpoints under /v1/.

Request GET /v1/calls/{id} for a call or GET /v1/messages/{id} for a message, using the id returned when you created it.

Search with POST /v1/numbers/search, then provision the one you want with POST /v1/numbers/provision. Numbers are available in 191 countries.

A 200 or 201 status with a JSON body. Errors return a 4xx or 5xx status, and the docs list what each code means.

Yes. Register a webhook with POST /v1/webhooks and subscribe to call.completed. Message and recording events work the same way.

On the docs page, which has limits for each plan and a table of error codes. This page is the endpoint reference.

Start building

One workspace, every conversation.
See what a real phone stack does.

Full API access, 5 official SDKs, and a sandbox environment. No telephony knowledge required.

Compliance with applicable regulations required.