The DIDWW REST API is here!

Interfacing with our services through an API is critical to many of our customers, and we have now released the API 3 platform, our API for the future.

API 3 provides a simple yet powerful interface that allows customers to include DIDWW services within their own business processes. As such, this interface is the ideal tool for building alternative dashboards, developing mobile apps and automating front and back-end applications.

The API 3 differs from our previous API versions by the inclusion of functionality and flexibility that brings customers much closer to our core processes and capabilities, allowing them to build their own custom and scalable VoIP-enabled cloud services.

We have specifically designed this REST API as a fully compliant implementation of the JSON API specification version 1.0, so as to provide feature-rich, simple, consistent interfaces for maximum efficiency of network resources. Full versioning is supported for API 3, allowing customers to manage and control their upgrade options and to manually change versions as required.

This initial version has a feature set that makes it largely comparable with most of our previous API functions, including coverage, CDR and DID management. New functionality has been added such as trunk group management and an enhanced DID ordering process, allowing customers to choose between bundled DIDs (including 2 dedicated channels) or unbundled DIDs where capacity is provided by metered or flat-rate channels. Additional functionality will be available in the near future, including full capacity management, porting and address registration, SMS routing and advanced service configuration options.

New accounts registering with DIDWW after 1st November 2017 will no longer receive access to old API versions. However, we will continue to support active users of all previous API versions, as we understand how painful it is when one-sided decisions force others to change business logic or process, consume expensive development time and cause unnecessary distractions. This commitment is in line with our stated company philosophy and policy.

We encourage our current API users to explore the structure and capabilities of this new interface and discover the advantages of migrating the current implementation to API 3, that will support our future services and will be aligned with our development efforts. The adaption of this new API version will also help us to reduce the efforts that we have to apply in supporting backwards compatibility, and will allow us to develop and expand new core functionality and services faster.

It is important to note, that for users of API 2 who had implemented reseller functions such as sub-customer accounts or billing capabilities, for example DIDReseller platform users, these facilities will not be available in API 3. Our experience with this business model revealed insurmountable challenges that we are not in the position to solve in the foreseeable future. There are other companies that specialize in billing software that provides solutions for these challenges, and these products may be used in conjunction with API 3 to offer a fully integrated solution for resellers. We will be assisting our resellers by searching and exploring these possible integrated solutions and we will publish a list of recommended vendors and integrators.

We look forward to receiving ideas and feedback regarding this new version of API 3.