56 posts tagged with "New Feature"

We are excited to announce the latest addition to our long list of supported platforms. Our C# section now has a new template for a .NET Standard library in addition to the already supported PCL and UWP templates. This library targets .Net Standard 1.3.

Usage of discriminators is already supported by our code generation engine. We are happy to announce that now support for using discriminators has also been added to AngularJS SDK.

• Discriminator is a field that is used to differentiate between a parent model and models that inherit from it.
• The response is deserialized into the parent model or one of its child classes by inspecting the discriminator field's value in the response.
• Using a discriminator field, you can build leaner models by not having to build unions of fields needed by a polymorphic response.

Please generate your SDK again if you want to use this feature.

OAuth 2.0 support was recently added to the API Editor and Code Generation engine. Now the support is added to Transformer as well as import/export in the Dashboard.

Usage of discriminators is already supported by our code generation engine. We are happy to announce that now support for using discriminators has also been added to Node.

• Discriminator is a field that is used to differentiate between a parent model and models that inherit from it.
• The response is deserialized into the parent model or one of its child classes by inspecting the discriminator field's value in the response.
• Using a discriminator field, you can build leaner models by not having to build unions of fields needed by a polymorphic response.

Please generate your SDK again if you want to use this feature.

Swagger supports response and schema examples as can be seen from their documentation on adding examples. If your API description contains response or schema examples, then the exported Swagger file will be populated with these examples.

Our API editor and Code Generation engine now supports OAuth 2.0 for authentication in the generated SDKs.

OAuth 2 enabled SDKs will help developers in:

• Obtaining consent from user
• Acquiring access token
• Refreshing tokens when they expire
• Making authorized API calls

You can read more about OAuth 2.0 in APIMatic editor and Code Generation engine here.

You can now set Composer Package Name for PHP SDKs being generated.

This will affect the name generated in the composer.json file. Leaving it empty will generate the a fallback package name based on your API name.

Good news! You can now export your existing API description files to WSDL. The generated WSDL can be utilized in generating server interfaces using VS developer tools in addition to other benefits. The WSDL generated follows the WSDL 1.1 format specified at https://www.w3.org/TR/wsdl.

Now you can upload a ZIP file containing your Postman Collection file along with any Postman Environment Files. That way we will extract values for your environment variables from the Environment files and give a better output during conversions on the Transformer or when importing APIs to your Manage APIs page. Support for Postman data dump files has now been added as well.

NodeJS SDKs will now return promises in endpoint calls, as an alternative to accepting callbacks.

• We use ES6 Promises which is based on Promises/A+ and is interoperable with most Promise-based implementations.
• Callbacks are still supported (for backward-compatibility) but are now optional.

Re-generate your NodeJS SDK to get the new Promise-enabled SDK implementation now.