Daniel Tolbert dtolb

Food Stuff

1 Onion
5 Carrots
All Purpose Flour
Beef Broth

--

Other stuff

Bandwidth Dashboard REST API Documentation API documentation version v1

/accounts

The account is the root resource for many of the operations in the Bandwidth Dashboard API.
The account is represented by an account id, which is the resource that represents a Bandwidth customer, providing a root resource for all of the customer's attributes and services
The API calls that are used to manage the details of a customer account, and to manage the resources that a Bandwidth customer has access to or control over, are accessed through the /accounts resource.

Results

My Suggestion

Moving forward, everything is done using Swagger. Ideally the code should contain the swagger, but until we're ready, keep the code/swagger decoupled.
IRIS Maintains the RAML documentation, but we should re-evaluate if we ever do merge IRIS/Catapult

Appointment Reminders. Powered by Bandwidth - Node.js/Express

This is an example of the small amount of work required to migrate an existing Twilio application to Bandwidth.

The original Appointment Reminders can be found over at Twilio's website.

Migrating to Bandwidth

Migration to Bandwidth for Appointment Reminders is VERY Easy

Airtng App: Masked Numbers Powered By Bandwidth

This is an exmaple of the reasonable amount of work required to migrate an existing voice and messaging application from Twilio to Bandwidth.

The original Airtng demo can be found over at Twilio's website -or- Github Profile.

Masked Numbers help protect your customers' privacy by creating a seamless interaction by provisioning Bandwidth numbers on the fly. Route all voice calls and messages through your very own 3rd party. This allows you to control the interaction between your customers while putting your customer's privacy first.

Migrating to Bandwidth

Introducing dev.bandwidth.com

Over the past few months, we have been working to redesign our documentation page for our Communcations API Platform and Dashboard products.

Why the update?

As Bandwidth has grown as an API company, we wanted to refresh our documentation with a focus on the developers using the API.

So, we went out and gathered feedback from all our local developers and read blogs. Lots and lots of blogs. The biggest take-away was 'show me code!'. So we went out and searched different doc sites that put code first and rich with examples.

	{
	"codes": [
	"201",
	"202",
	"203",
	"204",
	"205",
	"206",
	"207",
	"208",

	## Regarding API ease of use, could you elaborate on where you are vs. Twilio or other competitors?

	### Where Bandwidth is easier:
	* More advanced use cases where the customer wants to control each and every aspect of their calls. Bandwidth's REST API implementation trades off immediate ease-of-use and rewards the more advanced user by exposing each event to the user.
	* Example: Creating a round-robin call flow where an incoming call can try to connect multiple phones (one at a time) then record the call whenever the call is bridged. Then when the call is over, ask the incoming caller to take a brief survey.
	* Bandwidth excels at number portability compared to competitors. At this point, porting requires a Dashboard and App platform account, but even still is way ahead of the competition.
	* Example: OTT app wants to allow users to port numbers to/from their service. Via Bandwidth, this can all be done via the API with few customer-support tickets.
	* Bandwidth is more likely to partner with enterprise custo

	using System;
	using System.Linq;
	using System.Threading.Tasks;
	using Bandwidth.Net;
	using Bandwidth.Net.Api;

	namespace ConsoleApplication
	{
	public class Program
	{

	Appointment Reminders. Powered by Bandwidth - Node.js/Express

	This is an example of the small amount of work required to migrate an existing Twilio application to Bandwidth.

	The original Appointment Reminders can be found over at Twilio's website.

	Migrating to Bandwidth

	Migration to Bandwidth for Appointment Reminders is VERY Easy