Reference · built on requestConnectorVoice & contact center

Bandwidth

Voice calls, recordings, messages, and number events from Bandwidth, with call and message actions on its network.

Request accessPricing ↗

About

Bandwidth is a carrier that sells its voice, messaging, and number services through APIs. The Programmable Voice API at voice.bandwidth.com creates and steers calls with BXML, the Messaging API at messaging.bandwidth.com sends SMS and MMS, and the Numbers API at api.bandwidth.com buys, ports, and provisions telephone numbers. Applications hold the callback URLs; Bandwidth posts call and message events to them and, for voice, reads back BXML that tells the call what to do next.

Through Fibric, an operator reads call state, recordings, and message delivery, then proposes a text, an outbound call, or a redirect of a live call. You approve; it runs once and leaves a receipt: what was sent, to which number, and the delivery result.

This is a reference listing. It documents what Fibric would read from Bandwidth and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Call state and history through GET /accounts/{accountId}/calls and /calls/{callId}, kept for 7 days after hangup
  • Call lifecycle webhooks from your Voice application: Initiate, Answer, Disconnect, DTMF, Machine Detection Complete, Recording Available, Transcription Available
  • Recording metadata, media, and transcriptions through /accounts/{accountId}/recordings and /calls/{callId}/recordings/{recordingId}
  • Message history through GET /users/{accountId}/messages, filtered by status, direction, carrier, and a 14-day date range
  • Message webhooks message-received, message-sending, message-sent, message-delivered, message-failed, and message-read on your Messaging application
  • Number order and event notifications through Numbers API subscriptions, including portout validation webhooks
  • Current account state through GET /accounts/{accountId}/statistics

Proposed actions

  • Target capability: propose an SMS or MMS through POST /users/{accountId}/messages, with a tag and an expiration
  • Target capability: propose an outbound call through POST /accounts/{accountId}/calls that your BXML then controls
  • Target capability: propose redirecting a live call to new BXML through POST /accounts/{accountId}/calls/{callId}
  • Target capability: propose a transcription of a saved recording through POST /calls/{callId}/recordings/{recordingId}/transcription

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Send an appointment reminder by text

    The operator drafts the reminder with a tag naming the appointment and an expiration before the slot. After approval, message-delivered or message-failed closes the loop on the record.

    With Appointment Reminder

  • Notify affected customers during an outage

    The operator proposes one message per affected number and paces the batch against the account queue so a 429 max-message-queue-size-exceeded never drops a notice. Delivery webhooks report who got it.

    With Outage Notice

  • Confirm a redelivery window by text

    When a carrier reports a missed delivery, the operator proposes an SMS offering the next window and reads the customer's reply from message-received to update the order.

    With Missed Delivery

  • Replay a webhook that never arrived

    If your endpoint was down past Bandwidth's retry window, the operator reconciles from GET /users/{accountId}/messages and the calls list and proposes the events to replay into your systems.

    With Webhook Replay

Requirements

  • A Bandwidth account with a user who holds the Credential access role to create API credentials
  • A Voice-V2 or Messaging-V2 Application with callback URLs, assigned to the Location that holds your numbers
  • Bandwidth telephone numbers provisioned to those Locations through the Numbers API or the Bandwidth App
  • An HTTPS callback endpoint that answers voice webhooks within 15 seconds and message webhooks within 10 seconds
Authentication
OAuth 2.0 client credentials: a Client ID and Client Secret from Account > API Credentials in the Bandwidth App, exchanged at https://api.bandwidth.com/api/v1/oauth2/token for a Bearer JWT that expires in 3600 seconds.

Limits

  • Voice accounts default to 5 calls per second and 100 active sessions; outbound calls queue for 5 minutes at the provisioned rate before a 429
  • Call records disappear 7 days after hangup and the recordings list is capped at 1000 entries; keep your own history
  • List Messages searches a 14-day window, and limit plus offset cannot exceed 10,000
  • Legacy API User username and password authentication is deprecated and is removed on December 2, 2026

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Bandwidth ↗

Questions and answers

How long does Bandwidth retry a webhook?
It depends on the product. Messaging callbacks are retried over 24 hours until your server returns HTTP 2xx, with a 10 second timeout per attempt. Asynchronous voice callbacks are retried once on a connection exception. Numbers order notifications are not retried; portout validation webhooks are retried 8 times over 40 minutes.
What happens when I send faster than my messaging rate?
Messages queue per account. Rate limits count segments, so a 2 segment message counts twice. When the queue is full the API returns 429 with type max-message-queue-size-exceeded and a message such as: your allowed rate is 60 messages per minute; the capacity of this queue is 900 messages (15 minutes).
How are callbacks secured?
Applications carry optional basic authentication credentials, a UserId and Password, that Bandwidth sends with every callback; the docs mark them as not required but highly recommended. Numbers subscriptions use RFC 7235 basic authentication, answering a 401 challenge with base64 credentials. Voice applications also take a CallInitiatedFallbackUrl with its own credentials.
Ask about Bandwidth

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Bandwidth through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy