We have released a fix for HTTP Bearer authentication type in our OpenAPI import/transformation which was previously treating JWT as the default bearer authentication type. However, this will no longer be the case unless the bearerFormat in OpenAPI explicitly declares the format to be JWT.

APIMatic V3 (codenamed Titan) is APIMatic's largest release to date, bringing some major improvements to the Code Generator, the API Portal and the portal publishing flow. This changelog covers the new features and improvements to the API Portal.

APIMatic V3 (codenamed Titan) is APIMatic's largest release to date, bringing some major improvements to the Code Generator, the API Portal and the portal publishing flow. This changelog covers the new features and improvements in the updated APIMatic Code Generator which now generates vastly improved SDKs.

APIMatic V3 (codenamed Titan) is APIMatic’s largest release to date, bringing some major improvements to the Code Generator, the API Portal and the portal publishing flow. It also brings some shiny new features and improvements to API Transformer which are covered as part of this changelog.

API Transformer now supports multiple examples as an alternative to providing a single example for components. This is a feature available in both OpenAPI v3.0 and RAML v1.0 API description formats and any future transformations between these will see minimized loss of the examples' information.

Complete support for multiple responses has been added to API Transformer across all major formats like OpenAPI, RAML, API Blueprint, etc. This means a major reduction in loss of information related to responses when converting between various formats. Note, that these changes can also affect how your import in the Dashboard works.

Support for union types and other type constructs (oneOf, anyOf, not) has now been added to API Transformer and can also affect how your import in the Dashboard works. Re-transform/re-import your files to get these latest changes. Learn more about how (and if) these changes will affect you if you use any of these constructs in your API specification file.

Our OpenAPI importers (both v2.0 and v3.0) have undergone a complete overhaul that includes some major performance improvements, bug fixes and other refinements.

As part of our ongoing work on support for multiple responses, we have released some related changes in RAML 1.0 that may change how your imported API entity looks like.

API Transformer now preserves XML examples and XML serialization attributes like XML node name, prefix, namespace, etc. which reduces loss of information when converting between popular formats that support XML like OAS, RAML, WSDL, WADL, etc.