DEVOPSdigest

SmartBear Software has released a major upgrade to SwaggerHub, the place for development teams to collaborate and coordinate the entire lifecycle of an API.

SwaggerHub users can now create organizations and teams to organize, share and collaborate on Swagger API definitions directly in SwaggerHub, where public and private APIs are centrally and safely stored in a single, easy to use SaaS product.

“As services move toward public APIs, the value of having accessible API definitions in the OpenAPI Specification Format is becoming more apparent to developers and service providers alike,” said Tony Tam, VP of Products, Swagger at SmartBear. “With free and paid accounts, SwaggerHub is moving the API beyond code and into a first-class software artifact. With its robust API, end users can access their API definitions from external tools, keeping a central source-of-truth for the service interface.”

SwaggerHub allows users to discover and view public API definitions in its public registry, which contains over 2,500 APIs. During development, or for internal or sensitive services, it is often necessary to limit access to API definitions and versions. SwaggerHub now supports the ability to keep APIs private to users designated as collaborators. Inside SwaggerHub, a fine-grained access control can now be assigned to APIs.

Users can also create organizations to associate their APIs and find public APIs under an organization namespace. Within the scope of an organization, teams can be created, allowing for a fine-grained association of users to logical groups. Now these teams of users can be given read-only or read-write permissions against multiple API definitions in a single step.

With the rapid adoption of the Swagger Specification, which has been donated to the Open API Initiative under The Linux Foundation, more developers have been benefiting from the value of a contract-first API design. SwaggerHub was developed by members of the core Swagger development team with the goal of elevating the importance of design before coding and collaboration on the intent of the API.