70 posts tagged with "New Feature"

The SDKs now support passing complex objects, including non-scalar types and collections, as HTTP header parameters in the request.

The Python SDK now supports reading test configurations from environment variables, reducing the need for hardcoded values in the SDK test setup.

Developers frequently rely on string representations of models for debugging and logging. Our recent update enhances the __str__ or equivalent methods for models in Python, Ruby, PHP, and Go SDKs, offering clear, human-readable outputs.

We’re introducing support for typed additional model properties across all SDKs, enhancing type safety and alignment with OpenAPI specifications.

We have added an autogenerated table of content in the documentation that contains all the top level headings and sub-headings. Using a table of contents make it easy to navigate through multiple sections across the documentation page. It also helps in getting a high level idea of what are the contents of the documentation before getting into the detail of it.

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.

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.

You can now export GraphQL schema files from your REST/SOAP APIs using API Transformer.