Developer

Developer Resources

BWT provides a real-time provisioning API for managing your services programmatically. No tickets. No portals with seventeen tabs. Just an API.

Platform

Our customer portal and API are available at app.bwt.io. The API is RESTful, returns JSON, and does what you’d expect.

Capabilities

Number Management

  • Search: Query available DID inventory by rate center, state, NPA, or NPA-NXX. Results include rate center, LATA, and pricing.
  • Provision: Activate numbers instantly via API. Numbers are routable within seconds of activation.
  • Configure: Set call routing (SIP URI, IP address, failover destinations), enable/disable features (CNAM, E911, T.38), and manage number-level settings.
  • Release: Release numbers you no longer need. Released numbers return to the available pool.

Port Management

  • Submit: Submit port-in requests with all required subscriber information and LOA.
  • Track: Monitor port status in real-time. Get notified when FOCs are issued, when ports complete, or when rejects require attention.
  • Manage: Supplement or cancel pending port requests as needed.

Call Routing

  • SIP Trunks: Configure your SIP endpoints, including primary and failover destinations.
  • Per-number routing: Override trunk-level routing on a per-number basis.
  • Call forwarding: Configure unconditional or failover forwarding per DID.

Reporting

  • CDRs: Access call detail records via API. Filter by date range, number, direction, and disposition.
  • Usage: Query current usage and billing data.

Authentication

API access requires an API key, issued through the customer portal. All API requests must be made over HTTPS.

SIP Technical Reference

Registration

We support both IP-based authentication (recommended) and SIP registration-based authentication.

For IP-based auth, configure your SIP endpoint to send traffic to the IP and port provided during onboarding. We authenticate by source IP.

Headers

We use standard SIP headers. Some specifics:

  • From: Your authenticated caller ID
  • To: The dialed number in E.164 format
  • P-Asserted-Identity: Accepted for caller ID when present and authorized
  • Diversion: Supported for call forwarding indication

Codec Negotiation

We offer G.711 (PCMU/PCMA) first in our SDP. G.729 is supported on select routes but G.711 is strongly preferred. If you send us an SDP with only G.729, it will work on most routes, but you may experience transcoding on some paths.

DTMF

RFC 2833 only. We do not support in-band DTMF detection or SIP INFO DTMF.

Getting Started

  1. Contact sales@bwt.io to set up an account
  2. Log in to app.bwt.io and generate your API key
  3. Start making API calls

We don’t publish a 47-page “getting started” guide because the API is designed to be self-evident. If you’ve integrated with a telecom API before, you’ll be up and running in an afternoon.

If you hit a wall, email support@bwt.io. We’ll help.