nexmo-dotnet V4.2.0

  • The NCCO component within the CallCommand object can now be a strongly typed Ncco rather than a JArray, for the sake of backwards compatibility Ncco is left as a JArray but there is now an option to set a strongly typed Ncco object NccoObj instead see https://developer.nexmo.com/voice/voice-api/code-snippets/make-an-outbound-call-with-ncco for a sample
  • Adding type safety for NCCOs and webhook events
  • Adding application_id and has_application to Numbers API