62 posts tagged with "New Feature"

For the past few months, we have been hard at work improving API Transformer to give our users good quality output for any of their conversions. This changelog highlights all improvements made and new features added which we plan to release in a few weeks from now. To get full advantage of these improvements, some of the users who import from various formats like OpenAPI/Swagger, API Blueprint, etc. may need to regenerate their portal/SDKs.

We have added support for adding contact information of the organization maintaining the API in our API editor.

We've added the ability to call API endpoints directly from the browser in our Developer Experience Portal for APIs. This is provided as an alternative to calling the API via our proxy.

Our Android, .Net, Go, Java, NodeJS, PHP, Python and Ruby SDKs now allow skipping verification of SSL certificates. To do this enable the CodeGen Setting Allow Skipping Certificate Verification and then set the corresponding configuration variable in the respective SDK.

We've rewritten our Developer Experience portal and are releasing it as a major version. The new version introduces several new features in addition to bug fixes to some long-standing issues.

Check out the changes and how to migrate to the new portal.

We have added a new CodeGen setting to allow disabling linting in our SDKs. If you would like to benefit from this feature then please enable the setting and generate your SDKs again.

Our Postman exporters (both versions 1.0 and 2.0) now support collection variables to better represent requests in cases where multiple servers are involved.

Our GO SDK has been revamped pertaining to multiple bug fixes and new features.

• It now supports OAuth 2.0 Bearer Token for authentication in the generated SDKs.
• It now has a base client that can be used as a single point of entry for the SDK.
• The singleton architecture for clients has been removed to ease up the use in multiple user environments.
• Numerous bug fixes and improvements.

You can now use multiple base URLs in your API description using the new Server Configuration. This feature allows you to

• Vary the Base URL between endpoints.
• Create multiple Environments and define different Base URLs for them.
• Templatize Base URL to allow for configuration using parameters in the client.

A property is nullable if it allows sending null (in case of JSON/YAML, etc.) or nil (in case of XML) as value. Several API description formats like Open API, RAML, etc. has support for nullable properties. Transformer now also supports this property and you can convert between different formats without losing this information.