What's New

• Swagger Import

Existing Swagger documentation can now be imported and used directly on Mashery without being forced to convert them to IO-Docs. This will help API Owners to leverage existing target API documentation created using OpenAPI specification.

• Caching

API Owners can now take advantage of the caching feature on Mashery. Using the feature, API responses can be cached at the Mashery layer with a configurable time-to-live (TTL) value. This can help improve the response times for API calls.



• Response Filters

By leveraging the response filters, APIs can be configured to filter out specific fields in the response, for specific or all API consumers. This can be achieved at the Mashery layer without having to modify the target API.

There have been scenarios where an API returning around 10 fields in the response is then expected to fetch around 3 fields and that too in a short span of time. But, there is a long process to follow before this can be achieved like modifying the code at target API, testing it, deploying it in lower environments and then finally moving it to production.



With TIBCO Mashery, it would be easier to tackle such scenarios, as it can be configured at Mashery and there is no need to touch the API code for this kind of a requirement.

There are many other salient features of the Mashery platform. Click here to see the full list of features.

If you have any ideas on how you’d like to see us tackle the above enhancements, we’d love to hear from you. And of course, should you have any feature requests of your own, please contact us at any time or share with all via the API Forum.