HTTP curl code samples now support dynamic XML in the body of the code. Also, support for populating initial values for endpoint parameters using examples (if provided) has been added.

If you have globally defined schemas that directly use oneOf, anyOf, not constructs or union types, you will be pleased to know that API Transformer now converts between formats by preserving the global structure of such schemas.

We now announce support in API Transformer for API components that have no specific type or in other words are said to have any type. Until now, a default type (string/object) was assumed for all such cases.

APIMatic now has good news for all those who use our SDKs. We now support all the popular features given below for the SDK generation in multiple languages. You can now use these features in your API specifications for generating SDKs.

We now support multiple authentication schemes and related information in our API Transformer for all applicable API description formats including OpenAPI, RAML, Postman and Insomnia. You can now convert between these formats without losing important authentication details.

Based on the various feedbacks given to us, we have enhanced our error messages shown on the API Portal visible to the users while making API calls via the API code playground. This release improves the message content by adding some more useful information to the older error message.

To make your API documentation even more comprehensive and user-friendly, we have added support to add multiple examples against each response status code. This includes support for response headers and multiple content types.

We have added some improvements to our existing support for how request body Content-Type headers were handled during import. These changes can reflect in your output for SDK/portal generation or API transformations.

The OAuth 2.0 authorization code grant flow in the API Portal has been improved to make it more comprehensive and user-friendly. This includes introducing cancellable actions, access token visibility and updates to the UI for selecting scopes or resetting the token.

The Discriminator object in OpenAPI v3 supports a set of mapping values that helps determine which schema to map to based on the discriminator property's value in the payload. We have now added support for this set of mapping values in our OpenAPI v3 import and export. Previously, only the key or title of each schema involved in the hierarchy was considered as its discriminator value or one provided using the x-discriminator-value extension.