Classic: Messaging V2 API Account Setup (UI)


Jessica Murray


This article references the ‘Classic’ interface in the Bandwidth Dashboard. Looking for the ‘New’ experience? Click here!


Table of Contents

Before We Get Started

Create an Application

Order Phone Numbers

Sending Messages

Related Links


Before we get started

  1. Have you downloaded Postman or have the ability to make an API request? 
    1. Postman is an app for easy RESTful API exploration. In this guide, we will use Postman to send messages using our new application.
    2. Screenshot.PNG
    3. Once you’ve downloaded Postman and created an account (if you don’t already have one), fill out the form on the Postman page to download the Messaging 2.0 collection of APIsScreenshot_1.png
    4. In order to fill out this form, you’ll need several pieces of information that can be located in the Bandwidth Dashboard:
      • Username and password
        • These are your credentials to log into the Bandwidth DashboardScreenshot_2.PNG
      • Account ID
        1. Once logged into the Dashboard, click on the Account menu
        2. Locate your Account ID at the top of the Account Overview sectionaccount_id.png
      • Sub-Account 
        • If you have an existing Sub-Account, from top Navigation menu (screenshot below) click "Account," then "Sub-accounts".
        • You'll see the ID for the sub-account on the lefthand side of this screen. Enter this ID into the Postman form.subaccount.png


      • Messaging API Token and Secret
        • Bandwidth APIs use BASIC HTTP Authentication. You'll need to have your account ID, token, and secret to make API calls.
        • You may already have a Token and Secret that you can enter into the Postman form, but if you need a new set of credentials, you’ll need to follow the steps below.
        • In the Dashboard, navigate to the Applications menu. In the top right of your screen, you’ll see a link for API credentials.Screenshot_6.PNG
        • Click the button to CREATE NEW and then copy the credentials into a safe place for future use. Token and Secret pairs will not be visible after you leave this screen.Screenshot_7.PNG
  1. Once you’ve gathered all the information needed to complete the Postman Collection form, Click the “Run in Postman” button at the bottom of the page.            Screenshot_8.PNG
  2. The collection should now appear in Postman when you toggle to the Collections tab.Screenshot_9.PNG


Create an Application

  1. Now that we’ve taken care of the prerequisites, we’re ready to create an Application. Start by clicking the Applications menu in the dashboard.
  2. Create New 
  3. Enter your Application name
  4. Your Application ID is created for you
  5. Enter your Callback URL (this is the URL of your server)
  6. Create ApplicationScreenshot_10.PNG

Create a Location

Once you’ve created your Application, we’ll need to associate it with a Location. If you have an existing Location, you’ll choose the 'Associate a location with this application' link. If not, you’ll need to click the link to 'Create a location'.

You can read more about the steps for creating your Location as well as descriptions of the fields in the 'Add a Location' provisioning box in our support article.


  1. When creating a Location, click 'Account', 'Locations'
  2. Then 'Add Location'.
  3. Select the Sub-account that the Location will be associated with
  4. And enter a name for your Location.
  5. Select the SMS and MMS settings appropriate for your account.
  6. When selecting HTTPV2 Messaging (if your SMS Protocol is HTTP), you'll need to use the drop down to assign the Application we just created to this Location.
  7. After selecting all of the appropriate settings for your Location, click Submit.


Order Phone Numbers

  1. Now that we’ve done all the set up work for our application, we need to order a phone number to use to send text messages.
  2. In the Dashboard, use the Learning Lab & Support link to find the Quick Start guide for “Order New Phone Numbers.”   Screenshot_13.PNG
  3. Follow along with the guide and once your order/purchase has been completed, you'll land on the page below. Click the order ID to open the order.    Screenshot_14.PNG
  4. Scroll down the page till you see the number you ordered and use the Copy to Clipboard button to grab the number. This is the number you'll use to send and receive messages with your Application.Screenshot_15.PNG


Sending Messages

  1. At this point you should have completed the following: 
    1. Downloaded Postman and filled out the Postman Collection form with your individual credentials and potentially created a Sub-Account and Location in this step.
    2. Created an Application
    3. Created an Application
  2. Let’s head over to Postman and see what it looks like to actually send a message.
  3. Open Postman and toggle over to Collections. Use the drop down to open the Bandwidth Messaging 2.0 Collection and then click Send Text Messages.Screenshot_16.PNG
  4. Click “POST Send Text Message” and then click into the Authorization tab.
    1. Confirm your Token and Secret are entered here for your Username and Password.
    2. Enter your Dashboard Account ID for the {{userID}}.Screenshot_17.PNG
  5. Now let’s move over to the Body tab in Postman.
    1. Enter the following information then click the Send button:
      1. From: The number we ordered in the previous section of the guide.
      2. To: The number you’re sending a message to.
      3. Text: Update with the message you want to send
      4. ApplicationID: From your Application in the Dashboard      
    2. You should see a Status of 202 Accepted and a message completed to the receiving party.
  6. Message Parameters






One of your telephone numbers the message should come from (must be in E.164 format, like +19195551212).



The phone number the message should be sent to (must be in E.164 format, like +19195551212).



The contents of the text message (must be 2048 characters or less).



The ID of the Application your from number is associated with in the Bandwidth Phone Number Dashboard.


Related Links

Article is closed for comments.