SwaggerHub Product Updates: Custom Webhook Headers, OAS 3.0 Github Sync Support, and More

  December 06, 2018

As 2018 comes to a close, we are excited to see how far both the Swaggerhub solution and open source tools have evolved over the last year. In addition to our ongoing minor fixes and usability updates, there were a series of new features that were introduced into the tool this last month that we wanted to take a moment to highlight.

Custom Webhook Headers

SwaggerHub offers out-of-the-box integrations with many of the leading API gateways, management tools, and repository systems. But we’ve also heard from many existing SwaggerHub users that they need easier support for integrating with internal processes or services that require a specific header.

With the addition of custom headers in our webhook integration, we can now talk to those other services directly from Swaggerhub. This eliminates the need for additional processes or workflows to handle translating data. Thisopens up the number of services we integrate with in a huge way.

We will be exploring some of the interesting options for using custom webhooks in the coming weeks!

Persistent Workspace Customization

Swaggerhub has always been a platform that is designed to enable developers, architects and consumers to work more efficiently during the API design and development process. A key piece of enabling our users is to allow them to customize their workspace. Over the last few months, we’ve rolled out a handful of new features focused on the workspace – including a light/dark mode toggle, variable editor text sizes, and navigation panels.

With our recent updates, we now support persistent workspace configuration which means that regardless of how frequently you use Swaggerhub, or what you might consider to be the ‘perfect setup’, it will always be there the next time you log into the tool.

Repository Sync for OpenAPI 3.0

Support for version 3 of the OpenAPI specification continues to expand, with the ability to sync with external repositories from within the tool. This allows new or existing v3 definitions to connect to platforms like Github and Bitbucket, and to dynamically push both the specification and code generation libraries out with each new save.

This not only keeps development resources synced up but opens the possibility to have an always up-to-date set of client SDKs available to pull from a GIT repository system.

These were just some of the biggest improvements to the SwaggerHub platform in November. We have more to come before the end of the year, so keep an eye out for another announcement before the end of 2018!

Thanks for reading! Looking for more API resources? Subscribe to the Swagger newsletter. Receive a monthly email with our best API articles, trainings, tutorials, and more. Subscribe