Here at APIMatic, we are excited to finally announce support for OpenAPI's newer version v3.1 in all our major offerings including API Transformer, Developer Experience Portal and Code Generation. This format has now become a part of our ever-growing list of supported input and output formats.
Based on internal and customer feedback, we have revamped our validation messages shown to users during import or generation of artifacts like SDKs/Portal, etc. This release improves message content, introduces a couple of new validation messages and changes severity of some of the older messages.
APIMatic's PHP SDKs have been refactored to immutable clients and now support PHP 8.0 with updated dependencies. All static analysis and linting issues have been resolved, support for optional and nullable has been added along with a new restructured authorization flow, and much more.
We have added support for a RAML annotation that lets you define unit-tests for your RAML v1.0 methods within your specification. These unit-tests are then converted automatically to language-specific tests upon SDK generation.
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 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. 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. 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.