Use Multapplied’s open API to deliver more value internally than just revenue.

API usage

We’ve been running system maturity assessments recently with our partners – and we’re learning just as much as they are. In this post, we list five (out of the many) ways to take advantage of Bonded Internet’s API (Application Programming Interface).

Below, you’ll find five common uses for the API – if you’d like to discuss other options, please don’t hesitate to contact us and we’ll be happy to discuss the possibilities of your vision.

customer_portal

 

1. Building a Customer Portal

Many of your customers will want to look at their throughput graphs and perhaps have the ability to change Quality of Service profiles to better suit their changing operational strategies. For customers with many sites, it may also be a way to help you reduce support costs as your customers can look at their own information in detail and troubleshoot issues themselves.

Monitoring

2. Plugging Bonded Internet™ metrics into your Monitoring System

In your NOC, you may want to have real-time metrics tied to activity related to your Bonded Internet™ customers. With our API, interfacing with your NMS application is very straight-forward. We have a direct link to NagiOS from our User Interface, but other systems integrate nicely using our API.

billing_integration

3. Giving Bonded Internet a SKU in your billing platform

So, you’ve got the service set up, you’re starting to sell it, but charging and invoicing is still a manual process. Through simple calls to the API, Service Providers can easily push or pull information into or out of their billing platform. Setting up Bonded Internet™ as a line item is easy, but you can also set up billing for specific features in the event that you want to take multiple flavours of Bonded Internet™ to market.

Click here for a demonstration of Bonded Internet™

 

mass_provisioning

4. Excel™ to Bonded Internet™ for Mass Provisioning

We’ve seen it before where a partner has uprooted other services (MLPPP, Load/Link Balancers, etc.) in favour of Bonded Internet™. In such cases, the partner uses the API to mass provision thousands of sites at once. Essentially, the bonder (CPE device) is imaged, each is shipped to the location, and the box will configure itself based on the node key provided. All of the information is uploaded to the configuration server through an API call and a spreadsheet that includes such information as: IP addresses, Site Addresses, Leg types, Speeds, etc. This API usage saves hundreds of thousands of dollars over rolling trucks.

best-practices

5. Network Maintenance Audits

Through the API, service providers can set up minimum standards for service delivery and can use the API to audit their customers and their internal environments to make sure they meet the requirements. Things to look for include Disk Space, Average CPU usage, Disk Errors, Feature usage and settings and much more. Triggers can be set up through SNMPD to alert your support staff to abnormalities in the network.