v2.2.2

• Updated jose-jwt to 2.3.0 which is reported to address key loading issues.

v2.2.1

• Fixed NuGet dependencies; testing shows they are now being correctly included when performing install-package.

v2.2.0

(No changes from rc2)

• Allow PKCS#8 formatted private keys; auth key parser logging.
• Expose internal API request methods to allow custom API calls from library consumers as some new Nexmo API endpoints may not be immediately supported.
• Allow override of request credentials per API call.
• Optional configuration and request logging.
• Support signed requests via security key.
• Optional API request rate limiting.

v2.2.0-rc2

• Allow PKCS#8 formatted private keys; auth key parser logging.

v2.2.0-rc1

• Expose internal API request methods to allow custom API calls from library consumers as some new Nexmo API endpoints may not be immediately supported.
• Allow override of request credentials per API call.
• Optional configuration and request logging.
• Support signed requests via security key.
• Optional API request rate limiting.

v2.1.2

• Look for appsettings.json (netcore webapp convention)
• Ensure XML config parser only looks for keyvalues inside <appSettings> and <connectionStrings> elements.
• Gracefully ignore elements with key attribute but not value attribute.

v2.1.1

• Look for <executing process>.exe.config file for XML configuration.

v2.1.0

• User-Agent reporting. You may also append an application-specific ID via settings.json.
• [BREAKING] Support web.config XML. This has changed the settings.json structure slightly. Please check the README for details.

v2.0.0

• NumberInsight basic + standard support
• NumberVerify control call
• JWT token generation
• Application API support
• Application-based call API support
• .NET Standard 1.6 support
• [BREAKING] Moved configuration from app.config to settings.json
• [BREAKING] Nexmo.Api.Voice static class has been deprecated - you must move to the new Voice calls inside the new Nexmo.Api.Voice namespace. See the Nexmo docs for details.

JWT notes:

• When registering a new application, make sure you save the private key. This library does not (currently) take care of this for you.
• Make sure your saved private key is ASCII (not UTF-8, no BOM) - http://stackoverflow.com/questions/1068650/using-awk-to-remove-the-byte-order-mark

v1.0.0

Initial release with full support of API