Twilio is the company that taught a generation of developers that a phone call could be an HTTP request. Most people still think of it as “the SMS API.” The catalog tells a different story — 35 distinct APIs that together form a full communications control plane, not a single send-a-text endpoint.
It’s a useful provider to look at from the apis.io angle because Twilio committed early to the discipline most providers still avoid: one product, one spec. Each channel and each operational concern ships as its own surface.
What’s actually in the surface
The 35 APIs decompose into recognizable bands:
- Channels —
Messaging,Voice,Video,Conversations,Notify,IP Messaging,Media. The send-and-receive primitives across every modality. - Identity and trust —
Verify,Lookup,Trust Hub. Phone verification, number intelligence, and the regulatory compliance layer (A2P, brand registration) that increasingly gates messaging. - Routing and orchestration —
Studio,Task Router,Proxy,Routes,Flex,Frontline. The flow logic and contact-center surfaces that sit above raw channels. - Numbers and connectivity —
Numbers,Elastic SIP Trunking,Super SIM,Wireless,Microvisor. Provisioning phone numbers and the IoT/cellular connectivity layer. - Platform and operations —
Accounts,Monitor,Events,Insights,Intelligence,Pricing,Marketplace,Serverless,Sync,Bulk Exports. Account management, observability, conversational intelligence, and the serverless runtime. - Email —
SendGrid Email, folded in after the acquisition.
What’s interesting about the shape
A few things stand out once you see all 35 side by side:
- The control plane is separate from the data plane.
Accounts,Numbers,Trust Hub, andPricingare about configuring the platform.Messaging,Voice, andVideoare about running traffic through it. That split is exactly the structure agents need to provision once and then operate continuously. - Intelligence got its own surface.
IntelligenceandInsightsare not bolted onto Voice — they are independent APIs that consume the output of calls. That’s the pattern: derived value as a first-class, separately-callable product. - Compliance is an API, not a form.
Trust Hubturns brand and campaign registration into a programmable surface. As messaging regulation tightened, Twilio made the regulatory envelope itself callable.
The takeaway
Thirty-five specs is the right count for a company most developers reduce to one. Twilio is the canonical example of decomposing a platform by operational role — channel, identity, routing, connectivity, platform — so that a developer or an agent can call exactly the surface it needs without dragging in the rest. Walk the full surface on the Twilio provider page, and borrow the pattern: a clean spec per product beats one monolithic contract every time.