Bandwidth
Bandwidth is a leading cloud-based communications platform providing voice, messaging, emergency calling, phone number management, multi-factor authentication, and toll-free verification APIs. Built on Bandwidth's own Tier 1 network, the platform delivers enterprise-grade reliability for CPaaS applications.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Bandwidth the way a machine reads it — 249 machine-readable artifacts across 3 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Bandwidth scores 53.7/100 (developing), with a separate agent-readiness read of 27/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Put this on your own site. The badge is drawn live from Bandwidth's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/bandwidth/"
title="Bandwidth on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/bandwidth.svg"
alt="Bandwidth Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>
[](https://providers.apievangelist.com/providers/bandwidth/)
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/bandwidth/"
title="Bandwidth on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/bandwidth/card.svg"
alt="Bandwidth Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>
More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Bandwidth
Each block below is one kind of artifact we hold for Bandwidth. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 8
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Bandwidth Calls API
Create, retrieve, and manage phone calls. Supports outbound call creation, call state queries, and in-progress call modifications using BXML or redirect URLs.
Bandwidth Conferences API
Create and manage multi-party conference calls. Supports adding and removing members, muting, holding, and playing audio to conferences.
Bandwidth Emergency Notification Recipients API
Configure notification recipients who receive alerts when 911 calls are made from your endpoints.
Bandwidth Endpoints API
Manage 911 endpoints that represent end users of your service. Endpoints are identified by Alternate End User IDs (AEUIs) and are associated with locations for emergency routing.
Bandwidth Locations API
Provision and manage physical locations (addresses) for 911 emergency services routing. Locations are validated against the Master Street Address Guide (MSAG) for accuracy.
Bandwidth Media API
Upload, retrieve, and manage media files for use in MMS messages. Supports files up to 3.75 MB with 48-hour retention.
Bandwidth Messages API
Send and retrieve SMS and MMS messages. Supports single and group messaging, delivery receipts, and message history queries.
Bandwidth Recordings API
Manage call recordings including retrieval of recording metadata, audio files, and transcription of recorded audio content.
Scroll within the panel for all 8 ·
Postman Collections 18
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Scroll within the panel for all 18 ·
Open Collections 22
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONBandwidth Emergency Calling Available Numbers API
OPEN COLLECTIONBandwidth Emergency Calling Available Numbers Calls API
OPEN COLLECTIONBandwidth Emergency Calling API
OPEN COLLECTIONBandwidth Emergency Calling Available Numbers Endpoints API
OPEN COLLECTIONBandwidth Emergency Calling Available Numbers Locations API
OPEN COLLECTIONBandwidth Emergency Calling Available Numbers Media API
OPEN COLLECTIONBandwidth Emergency Calling Available Numbers Messages API
OPEN COLLECTIONBandwidth Messaging API
OPEN COLLECTIONBandwidth Emergency Calling Available Numbers MFA API
OPEN COLLECTIONBandwidth Emergency Calling Available Numbers Orders API
OPEN COLLECTIONBandwidth Emergency Calling Available Numbers Port-Ins API
OPEN COLLECTIONBandwidth Emergency Calling Available Numbers Recordings API
OPEN COLLECTIONBandwidth Emergency Calling Available Numbers SIP Peers API
OPEN COLLECTIONBandwidth Emergency Calling Available Numbers Sites API
OPEN COLLECTIONBandwidth Voice API
OPEN COLLECTIONScroll within the panel for all 22 ·
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Bandwidth GraphQL Schema
This document describes a conceptual GraphQL schema for the Bandwidth cloud communications platform. Bandwidth provides voice, messaging, phone number management, multi-factor a...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Bandwidth Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Bandwidth Finops
FINOPSFeatures 16
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 16 ·
Event Specifications 2
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Bandwidth Messaging Events
Bandwidth Messaging API sends webhooks to your application for real-time message delivery notifications and inbound message alerts. Callbacks are sent via HTTP POST to the callb...
ASYNCAPIBandwidth Voice Events
Bandwidth Voice API sends webhooks (BXML callbacks) to your application for real-time call event notifications. These webhooks inform your application of call state changes and ...
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Bandwidth Context
JSON-LDSpectral Rules 3
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
JSON Schema 54
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Bandwidth Call
JSON SCHEMABandwidth Message
JSON SCHEMABandwidth Phone Number
JSON SCHEMAEndpointListResponse
JSON SCHEMAEndpoint
JSON SCHEMALocationListResponse
JSON SCHEMALocation
JSON SCHEMANotificationRecipientListResponse
JSON SCHEMANotificationRecipient
JSON SCHEMACreateMessageRequest
JSON SCHEMAError
JSON SCHEMAMedia
JSON SCHEMAMessageList
JSON SCHEMAMessage
JSON SCHEMAError
JSON SCHEMAMfaMessagingRequest
JSON SCHEMAMfaMessagingResponse
JSON SCHEMAMfaVerifyRequest
JSON SCHEMAMfaVerifyResponse
JSON SCHEMAMfaVoiceRequest
JSON SCHEMAMfaVoiceResponse
JSON SCHEMAAddress
JSON SCHEMAAvailableNumber
JSON SCHEMAAvailableNumbersResponse
JSON SCHEMADisconnectRequest
JSON SCHEMADisconnectResponse
JSON SCHEMAFeatureOrderRequest
JSON SCHEMAOrderListResponse
JSON SCHEMAOrderRequest
JSON SCHEMAOrderResponse
JSON SCHEMAPhoneNumberListResponse
JSON SCHEMAPhoneNumber
JSON SCHEMAPortInListResponse
JSON SCHEMAPortInRequest
JSON SCHEMAPortInResponse
JSON SCHEMASipPeerListResponse
JSON SCHEMASipPeer
JSON SCHEMASiteListResponse
JSON SCHEMASite
JSON SCHEMAError
JSON SCHEMAVerificationListResponse
JSON SCHEMAVerificationRequest
JSON SCHEMAVerification
JSON SCHEMACall
JSON SCHEMAConferenceMember
JSON SCHEMAConference
JSON SCHEMACreateCallRequest
JSON SCHEMAError
JSON SCHEMARecording
JSON SCHEMATranscriptionRequest
JSON SCHEMATranscription
JSON SCHEMAUpdateCallRequest
JSON SCHEMAUpdateConferenceMemberRequest
JSON SCHEMAUpdateConferenceRequest
JSON SCHEMAScroll within the panel for all 54 ·
JSON Structure 54
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Bandwidth Call Structure
JSON STRUCTUREBandwidth Message Structure
JSON STRUCTUREBandwidth Phone Number Structure
JSON STRUCTUREEmergency Calling Endpoint List Response Structure
JSON STRUCTUREEmergency Calling Endpoint Structure
JSON STRUCTUREEmergency Calling Location List Response Structure
JSON STRUCTUREEmergency Calling Location Structure
JSON STRUCTUREEmergency Calling Notification Recipient Structure
JSON STRUCTUREMessaging Create Message Request Structure
JSON STRUCTUREMessaging Error Structure
JSON STRUCTUREMessaging Media Structure
JSON STRUCTUREMessaging Message List Structure
JSON STRUCTUREMessaging Message Structure
JSON STRUCTUREMfa Error Structure
JSON STRUCTUREMfa Mfa Messaging Request Structure
JSON STRUCTUREMfa Mfa Messaging Response Structure
JSON STRUCTUREMfa Mfa Verify Request Structure
JSON STRUCTUREMfa Mfa Verify Response Structure
JSON STRUCTUREMfa Mfa Voice Request Structure
JSON STRUCTUREMfa Mfa Voice Response Structure
JSON STRUCTUREPhone Numbers Address Structure
JSON STRUCTUREPhone Numbers Available Number Structure
JSON STRUCTUREPhone Numbers Available Numbers Response Structure
JSON STRUCTUREPhone Numbers Disconnect Request Structure
JSON STRUCTUREPhone Numbers Disconnect Response Structure
JSON STRUCTUREPhone Numbers Feature Order Request Structure
JSON STRUCTUREPhone Numbers Order List Response Structure
JSON STRUCTUREPhone Numbers Order Request Structure
JSON STRUCTUREPhone Numbers Order Response Structure
JSON STRUCTUREPhone Numbers Phone Number List Response Structure
JSON STRUCTUREPhone Numbers Phone Number Structure
JSON STRUCTUREPhone Numbers Port In List Response Structure
JSON STRUCTUREPhone Numbers Port In Request Structure
JSON STRUCTUREPhone Numbers Port In Response Structure
JSON STRUCTUREPhone Numbers Sip Peer List Response Structure
JSON STRUCTUREPhone Numbers Sip Peer Structure
JSON STRUCTUREPhone Numbers Site List Response Structure
JSON STRUCTUREPhone Numbers Site Structure
JSON STRUCTUREToll Free Verification Error Structure
JSON STRUCTUREToll Free Verification Verification Request Structure
JSON STRUCTUREToll Free Verification Verification Structure
JSON STRUCTUREVoice Call Structure
JSON STRUCTUREVoice Conference Member Structure
JSON STRUCTUREVoice Conference Structure
JSON STRUCTUREVoice Create Call Request Structure
JSON STRUCTUREVoice Error Structure
JSON STRUCTUREVoice Recording Structure
JSON STRUCTUREVoice Transcription Request Structure
JSON STRUCTUREVoice Transcription Structure
JSON STRUCTUREVoice Update Call Request Structure
JSON STRUCTUREVoice Update Conference Member Request Structure
JSON STRUCTUREVoice Update Conference Request Structure
JSON STRUCTUREScroll within the panel for all 54 ·
Examples 54
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Bandwidth Call Example
EXAMPLEBandwidth Message Example
EXAMPLEMessaging Error Example
EXAMPLEMessaging Media Example
EXAMPLEMessaging Message Example
EXAMPLEMfa Error Example
EXAMPLEPhone Numbers Site Example
EXAMPLEVoice Call Example
EXAMPLEVoice Conference Example
EXAMPLEVoice Error Example
EXAMPLEVoice Recording Example
EXAMPLEVoice Transcription Example
EXAMPLEScroll within the panel for all 54 ·
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 8
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Click-to-Call
Embed outbound calling in web and mobile applications.
IVR Systems
Build interactive voice response menus with DTMF input and TTS.
A2P Messaging
Send application-to-person SMS campaigns at scale.
2FA / OTP
Add SMS or voice-based multi-factor authentication to applications.
Number Provisioning
Automate phone number procurement and assignment for customers.
E911 Compliance
Meet Kari's Law and RAY BAUM's Act requirements for enterprise voice.
Call Center
Build inbound/outbound contact center applications with recording.
Number Porting
Migrate existing phone numbers to Bandwidth programmatically.
Scroll within the panel for all 8 ·
Resources
Every other property we hold for Bandwidth — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 4
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/bandwidth · machine-readable index on apis.io
This is an independent, third-party profile of Bandwidth, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.