GatewayAPI vs. Vonage Communications APIs

While there are likely a variety of scenarios that would work well with Vonage [Communications APIs (formerly Nexmo)], implementations that need transactional message and response actions are a great fit. Our experience with transactional messaging has been really good and we are continuing to look at opportunities to expand our usage of this part of their service.

• I like the delivery speed, it's very instantaneous. As soon as the delivery status changes on the website, the message gets delivered. The rates are also cheap and affordable.
• The accuracy of the services and the non-stop supportive team.
• Simple API, easy to integrate with existing notification functionality in your Laravel apps.
• Ease of implementation. We needed less than one month to go live.

Incentivized

• Written documentation and discovery could be a lot better.

The overall usability of Vonage [Communications APIs (formerly Nexmo)] system for message delivery is sufficient for our implementation. Some improvements and additional reporting options in the account administration interface would increase our utilization of the post-delivery data further in order to provide further value-added features for our clients.

The product feels a bit like a black box since it's built to be an off-the-shelf solution so sometimes it feels like the only way to really understand it is to talk to an engineer directly as the documentation is so-so.

Nexmo is the best platform in the industry for sure. We don't use all the features that the API provides but we are really satisfied with the ones we use. We are sure this is the best solution in the market if you need to solve the communication in real time with your customers. When we have to build a new website we are going to support the solution with Nexmo.

Incentivized

• Allowed us to go to market faster (positive).
• Greatly limits our claim to quality as the ceiling on video quality is lower than other platforms (negative).