.NET SDK Update

.NET SDK Update

Published November 19, 2019 by Steve Lorello

The last couple of months have been a bit of a whirlwind here at Nexmo as I’ve been working on fixing bugs and upgrading the .NET SDK for you all.

More will be coming in the future, but we’ve cut a few new releases over the past couple of months, and I’d like to take some time out to tell you all about them.



In 4.0.1 we added the workflow ID parameter to verify requests. This version enables you, when sending off a Verify request to specify what process you want Nexmo to use for verification.

Those workflows are as follows—note that for our purposes an SMS message is an SMS text message and TTS refers to a text-to-speech voice call:

  • “1” – SMS -> TTS -> TTS
  • “2” – SMS -> SMS -> TTS
  • “3” – TTS -> TTS
  • “4” – SMS -> SMS
  • “5” – SMS -> TTS
  • “6” – SMS
  • “7” – TTS

For further info please check out the Verify Workflows documentation. Additionally, you can read the Flexible Workflows for Verify API article on how workflows take shape. Happy verifying!



  • Release 4.1.1 straightens out a bunch of dependencies in the NuGet package—that would have been transparent to most folks but needed to be addressed.


  • 4.1.2 adds full support for the signing of SMS messages and the validation of signed SMS messages. See our guide on leveraging this capability.


This version supports a fairly major upgrade to the SDK. We now have strongly typed NCCOs and webhook events! There is no longer a need to dynamically produce your own JSON when sending us NCCO’s or to figure out on your own what the structure of an event looks like.

To create your NCCO simply create a series of actions, construct an NCCO object with those actions, and invoke NCCO.ToString() to create your ncco.

If you would like to make an outbound call with one of these strongly typed NCCOs now you can! I know many of you are still using the old CallCommand Object that just accepted a JObject, that JObject is still acceptable. You now have the option of setting a NccoObj rather than the Ncco in the CallCommand to use a strongly typed NCCO. Like so:


With 4.2.1 it’s now possible to track in progress NCCOs straight out of the box with the Nexmo .NET SDK.

We fixed a bug where the incorrect RSA provider was being used on newer versions of .NET core off of windows platforms. I want to give a big shout out to one of our community contributors Fauna5 for their pull request for this!

Feel free to follow the .NET SDK on GitHub for real time updates.

If you have any questions, issues, or concerns please feel free to raise them there or find me @Steve Lorello in our Community Slack Channel and I’ll be more than happy to help.

Leave a Reply

Your email address will not be published.

Get the latest posts from Nexmo’s next-generation communications blog delivered to your inbox.

By signing up to our communications blog, you accept our privacy policy , which sets out how we use your data and the rights you have in respect of your data. You can opt out of receiving our updates by clicking the unsubscribe link in the email or by emailing us at [email protected].