Swaggerhub documentation

Swaggerhub documentation DEFAULT

with the SwaggerHub suite? _


In the first article about API design tools, we presented the Stoplight suite. For this second article, we will introduce the SwaggerHub suite from the swagger.io website from Smartbear.

Smartbear has been offering an open-source tool for testing web services for several years, called SoapUI.

SoapUI is essential for automating web services tests. It supports SOAP and REST formats and HTTP/HTTPS and JMS protocols.

One of SoapUI’s assets is the validation of WSDLs, the interfaces of web services.

With the massive arrival of REST APIs in the digitalization strategy of companies, Smartbear has developed the ReadyAPI tool which is a complete version of SoapUI for testing web services and APIs.


The SwaggerHub suite focuses on API design, i.e. defining the interface of services that will be exposed to partners or internal applications of the information system.

Swagger offers both an open-source and a pro version.

The main tool of the solution is Swagger UI which allows to graphically visualize the JSON file (or YAML) which defines the interface of an API, we talk about the OpenAPI standard (formerly Swagger, hence the name of the suite).

If the graphical representation of the interface is very well done, we can see in the following example that the JSON code is sometimes hard to read.

The editor allows you to have both the JSON code and the graphical rendering on the same page, while the tool displays the errors present in the JSON code.

The Pro version of SwaggerHub allows you to create a team and work on the same OpenAPI or Swagger files:

Swagger files can be automatically synchronized with GitHub.

SwaggerHub allows you to work in a team to define API interfaces, in a pure Design-First spirit. Clients can be created in the most popular languages, and stubs can be generated for services.

Combined with ReadyAPI for API testing, a complete solution is available for teams developing and deploying REST APIs. The documentation of the APIs will be easier to write, and the user experience will be improved.

Sours: https://astrakhan.fr/en/blog/how-to-design-and-document-your-apis-with-the-swaggerhub-suite/
  • Best API Lifecycle Management Tool!!

    • Reviewer Role: Data and Analytics
    • Company Size: 250M - 500M USD
    • Industry: Services Industry

    I have very good experience about this tool since day 1 when I integrated this into my spring boot project. I has very simple and user-friendly interface that's the reason everyone likes this tool as compare to other API management tool. It is very easy to configure. We can also ......

  • Swagger hub: API management tool

    • Reviewer Role: Analyst
    • Company Size: 250M - 500M USD
    • Industry: Services Industry

    Swagger hub is a tool used to design APIs. It is basically designed for small/midsize organizations that are engaged in API, management, designing, and testing. It helps us to accelerate the team design process without any loss in quality. Its integration with Bitbucket ......

  • bringing best core capabilities with furnished API service

    • Reviewer Role: Knowledge Specialist
    • Company Size: 10B - 30B USD
    • Industry: Manufacturing Industry

    SwaggerHub is one of the cutting-edge and most widely used solutions to design and manage the API for quick deployment across the organization and outside external sources. It's having the best UI connection with HTML and other scripting available in the market....

  • Excellent API Management solution tool for developers.

    • Reviewer Role: Applications
    • Company Size: 50M - 250M USD
    • Industry: Services Industry

    We are using this tool for approx 1 year to design-build, document, and deploy APIs. It enables us to integrate with third party software which makes an integration test easier....

  • Gives an ease for simple and reliable API documentation

    • Reviewer Role: Applications
    • Company Size: 10B - 30B USD
    • Industry: Services Industry

    An excellent option to streamline a large quantity of tasks related to the documentation of the software and creation of technical development report. Great performance and functionalities. Have been using it to document all the changes done in API so that entire development team ......

  • SwaggerHub - Best Tool For API Management

    • Reviewer Role: Applications
    • Company Size: 250M - 500M USD
    • Industry: Services Industry

    SwaggerHub is a jack of all trade in API management tools, it provides all the much-needed support for API development, designing, testing and documenting all the APIs in a very good manner with so much fewer efforts, this makes integration job lot easier, ultimately it leads ......

  • Best tool for collaboration and coordination across API life cycle!!

    • Reviewer Role: R&D/Product Development
    • Company Size: 50M - 250M USD
    • Industry: Services Industry

    My first experience about swagger hub is amazing I don't even imagine before integrating swagger that we can document our API's in such beautiful way. It has most likely user interface. Also it is very easy intergrade with our projects. It acts as a bridge between client ......

  • Excellent tool to implement API.

    • Reviewer Role: Analyst
    • Company Size: 50M - 250M USD
    • Industry: Services Industry

    I have using the swagger hub for approx 6 months and I can say I am very happy because designing API's here is to easy and fast. So I personally use Swagger for every product....

  • SwaggerHub : No installation -Ready to Test

    • Reviewer Role: Applications
    • Company Size: 250M - 500M USD
    • Industry: Services Industry

    overall great experience. Best part being no installations. We can easily set this up right from you r browser. Tried the free version for testing openApi and was just ready to use in Minutes. Easy to use UI....

  • Provides an ease to maintain the API documentation with other great features

    • Reviewer Role: Applications
    • Company Size: 10B - 30B USD
    • Industry: Energy and Utilities Industry

    Great to implement API development, Documentation, API testing and mocking the services. Documenting API is very easy with swagger and also helps to all the team members to work on the same updated code and gives the same understanding. ...

  • A good tool to apply API design governance in the efficient way.

    • Reviewer Role: Enterprise Architecture and Technology Innovation
    • Company Size: <50M USD
    • Industry: Transportation Industry

    My experience using SwaggerHub is good. It is a good tool to support API design and governance, to bring consistency and apply best practice across the organization....

  • The best way to document the API and share it with the team

    • Reviewer Role: Analyst
    • Company Size: 10B - 30B USD
    • Industry: Services Industry

    SwaggerHub helps to define services according to openAPI Specifications. Helps to keep the code at one place and other teams testing and frontend can easily integrate it. Reduces the dependancy on other teams. ...

  • SwagerUI an open API specification champion

    • Reviewer Role: R&D/Product Development
    • Company Size: 3B - 10B USD
    • Industry: Services Industry

    I use on a daily basis and I love it, because it is very is easy to use and share with other. It is much better than MuleSoft - Raml documentation in every sense....

  • Best tool to document your API

    • Reviewer Role: Applications
    • Company Size: 10B - 30B USD
    • Industry: Services Industry

    Feature to document while demonstrating is the best feature. Gives an ease to communicate requirement with the team members and customer. ...

  • SwaggerHub a good integrated API development platform

    • Reviewer Role: R&D/Product Development
    • Company Size: 30B + USD
    • Industry: Finance Industry

    SwaggerHub is still in the infancy stage at the moment as we ready this to be part of our development ecosystem. It is a good solution to design, manage and publish API. Hopefully, it will fast track deployment process within our organization....

See All 55 Product Reviews

Sours: https://www.gartner.com/reviews/market/full-life-cycle-api-management/vendor/smartbear/product/smartbear-swaggerhub
  1. Youtube unicorn cake
  2. Bts bottega veneta
  3. Gold foil background
  4. D16 engine vtec

API Development Tool - SwaggerHub

One way to improve the speed and quality of API development is to drive consistency and discipline across the API development workflow. Lexington Soft offers SwaggerHub, an integrated API design and documentation platform to support your team’s API Design workflow, accelerating API delivery and quality through standards and collaboration built on OpenAPI.

Powerful API Editor

SwaggerHub provides a powerful Editor that’s fully compliant with the latest OpenAPI standards. Its features include

  • Smart error feedback and syntax auto-completion
  • Ability to create API mocks automatically while you design
  • Embedded API design rules that reinforce standards in real-time
  • Domains for cataloging and reusing common OAS syntax across APIs

Screenshot of SwaggerHub

API Collaboration & Standardization

SwaggerHub fosters API collaboration and standardization across teams in enterprises by providing a single source of truth for API definitions. It

  • Provides Organization and Team Management so you know who owns what
  • Allows you to fork, compare or merge with an existing API
  • Enables Real-time commenting and issue tracking adjacent to the editor
  • Syncs API definitions with source control repositories & gateways

With SwaggerHub, you can generate interactive documentation automatically during design, making it easy for both API consumers and internal users to learn and work with your APIs.

SwaggerHub integrates with platforms such as AWS, apigee, GitHub, Bitbucket, and Azure, so that you can easily do things like push generating your API’s design and code to source control hosts, deploying API to API Management platforms, or triggering your Jenkins build.

Want to know if SwaggerHub will meet your needs for improving API design quality? Lexington Soft will gladly provide a sales demo and proof of concept, conduct product evaluations and even offer you a free trial!

As a SmartBear Elite partner, Lexington Soft is committed to providing the best after-sales support for our customers. We offer

For a more complete API readiness solution, Lexington Soft offers a suite of SmartBear tools that include

Build performance and quality into your APIs. Contact us today!

our offices

#7, 15th Avenue Harrington Road, Chennai, Tamil Nadu 600031, India


RMZ Infinity Center,
1st floor - Tower D, No. 3, Old Madras Road,
Benniganahalli village, Krishnarajpuram Hobli,
Bangalore, Karnataka 560016, India


52 Waltham Street
Lexington, MA 02421

© 2019-2020 Lexington Soft. ALL RIGHTS RESERVED.

Sours: https://www.lexingtonsoft.com/software-testing-tools/api-development-tool-swaggerhub/
Autogenerating Swagger Documentation with Node \u0026 Express

SwaggerHub introduction and tutorial

Last updated: Mar 30, 2020

Previously, I explored using the open-source Swagger UI project as a way to render your OpenAPI specification document. The same company that offers the free, open-source version of Swagger Editor and Swagger UI (Smartbear) also offers a premium version with more robust features. This premium version of Swagger Editor is called SwaggerHub. You can see a comparison of features between the open source and premium versions here.

You can see a demo of the sample OpenWeatherMap API on SwaggerHub here.

Note that Smartbear is one of the sponsors of my site.

Advantages of SwaggerHub

While the open-source Swagger Editor coupled with Swagger UI works, you’ll run into several problems:

  • It’s challenging to collaborate with other project members on the spec.
  • It’s difficult to gather feedback from reviewers about specific parts of the spec.
  • You can’t automatically provide the API in the myriad code frameworks your users might want it in.

When you’re working on REST API documentation, you need tools specifically designed for REST APIs — tools that allow you to create, share, collaborate, version, test, and publish the documentation in ways that don’t require extensive customization or time.

There’s a point at which experimenting with the free Swagger UI tooling hits a wall, and you’ll need to find another way to move to the next level. This next level is where SwaggerHub from Smartbear comes in. SwaggerHub provides a complete solution for designing, managing, and publishing documentation for your API in ways that will simplify your life as an API technical writer.

More than 15,000 software teams across the globe use SwaggerHub. As the OpenAPI spec becomes more of an industry standard for API documentation, SwaggerHub’s swagger-specific tooling can be essential.

SwaggerHub Intro and Dashboard

Smartbear is the company that maintains and develops the open source Swagger tooling (Swagger Editor, Swagger UI, Swagger Codegen, and others.) They also formed the OpenAPI Initiative, which leads the evolution of the Swagger (OpenAPI) specification.

Smartbear developed SwaggerHub as a way to help teams collaborate around the OpenAPI spec. Many of the client and server SDKs can be auto-generated from SwaggerHub, and there are a host of additional features you can leverage as you design, test, and publish your API.

To get started with SwaggerHub, go to swaggerhub.com and create an account or sign in with your GitHub credentials. After signing in, you see the SwaggerHub dashboard.

The dashboard shows a list of the APIs you’ve created. In this example, you see the OpenWeatherMap API that I’ve been using throughout this course.

SwaggerHub Editor

SwaggerHub contains the same Swagger Editor that you can access online. This editor provides you with real-time validation as you work on your API spec. However, unlike the standalone Swagger Editor, with SwaggerHub’s Swagger Editor, you can toggle between several modes:

  • Hide Navigation
  • Hide Editor and Navigation
  • Hide UI Docs
SwaggerHub's editor gives you more flexible viewing options

Most importantly, as you’re working in the Editor, SwaggerHub allows you to save your work. With the free Swagger Editor, your content is kept in the browser cache, with no ability to save the file in the cloud. When you clear your cache, your content is gone. As a result, if you use the standalone Swagger Editor, you have to regularly copy the content from the Swagger Editor into a file on your own computer each time you finish.

With SwaggerHub, you can save your specification document directly on SwaggerHub’s servers, or you can reference and store it in an external source such as GitHub.


SwaggerHub not only allows you to save your OpenAPI spec but also save different versions of your spec. As a result, you can experiment with new content by adding a new version. You can return to any version you want, and you can also publish or unpublish any version.

Versioning options for your OpenAPI file

When you publish a version, the published version becomes Read Only. If you want to make changes to a published version (rather than creating a new version), you can unpublish the version and make edits to it.

You can link to specific versions of your documentation, or you can use a more general link path that will automatically forward to the latest version. Here’s a link to the OpenWeatherMap API published on SwaggerHub that uses version 2.5.1 of the documentation: https://app.swaggerhub.com/apis/IdRatherBeWriting/open-weather_map_api/2.5.1/. To link to a specific version, include the version number in the URL. In contrast, this more general link (which omits a version number) automatically forwards to the latest version (which is 2.5.2): https://app.swaggerhub.com/apis/IdRatherBeWriting/open-weather_map_api/.

Versioning is helpful when you’re collaborating on the spec with other team members. For example, suppose the original version was drafted by an engineer, and you want to make major edits. Rather than directly overwriting the content (or making a backup copy of an offline file), you can create a new version and then take more ownership to overhaul that version with your own updates, without fear that the engineer will react negatively about overwritten/lost content.

When you publish your Swagger documentation on SwaggerHub, Swagger’s base URL () remains in the URL. Although this base URL isn’t customizable, you can add your company logo and visual branding as desired.

Key to the review process is the ability for team members to comment on the spec inline, similar to Google Docs and its margin annotations. When you’re working in SwaggerHub’s editor, a small plus sign appears to the left of every line. Click the plus button to add a comment inline at that point.

Inline commenting and reply features on SwaggerHub

When you click the plus sign, a comment pane appears on the right where you can elaborate on comments, and where others can reply. Users can edit, delete, or resolve the comments. This commenting feature helps facilitate the review process in a way that tightly integrates with your content. You can also collapse or show the comments pane as desired.

Few tech comm tools support inline annotations like this, and it wouldn’t be possible without a database to store the comments, along with profiles associated with the reviewers. This feature would be tedious to implement on your own, as it would require both a database and an authentication mechanism. This is all included in SwaggerHub.

Auto-Generate Client SDKs

Another benefit to SwaggerHub is the ability to auto-generate the needed client or server code from your specification. Client SDKs provide the tooling needed to make API requests in specific programming languages (like Java or Ruby).

In the upper-right corner, click the down-arrow and select Client or Server. Users have access to generate client and server SDKs in more than 30 formats.

Client and server SDK export capabilities

For example, suppose a user is implementing your REST API in a Java application. The user can choose to download the Java client SDK for extensive code that shows a Java implementation of your API. Other options include Ruby, Android, Go, CSharp, JavaScript, Python, Scala, PHP, Swift, and many more.

Some API documentation sites look impressive for showing implementations in various programming languages. SwaggerHub takes those programming languages and multiplies them tenfold to provide every possible output a user could want.

The output includes more than a simple code sample showing how to call a REST endpoint in that language. The output includes a whole SDK that includes the various nuts and bolts of an implementation in that language. (For more information on SDKs, see SDKs.)

Providing this code speeds implementation for developers and helps you scale your language-agnostic REST API to a greater variety of platforms and users, reducing the friction in adoption.

Export to HTML

Among SwaggerHub’s many options for generating client and SDK files is an HTML option. You can export your OpenAPI spec as a static HTML file in one of two styles: HTML or HTML2.

You can see a demo export of the OpenWeatherAPI API here: HTML or HTML2. Both exports generate all the content into an index.html file.

The HTML export is a more basic output than HTML2. You could potentially incorporate the HTML output into your other documentation, such as what Cherryleaf did in importing Swagger into Flare. (You might have to strip away some of the code and provide styles for the various documentation elements, and there wouldn’t be any interactivity for users to try it out, but it could be done.) In another part of the course, I expand on ways to integrate Swagger UI’s output with the rest of your docs.

The HTML2 export is more intended to stand on its own, as it has a fixed left sidebar to navigate the endpoints and navtabs showing six different code samples:

HTML export

Both outputs would need a healthy dose of custom styling to be usable.

Mocking Servers

Another cool feature of SwaggerHub is the ability to create mock API servers. Suppose you have an API in which you don’t want users to generate real requests. (Maybe it’s an ordering system where users might be ordering products through the API, or you don’t have test accounts/systems). Even so, you can still simulate responses that let users get a sense of how your API works.

Assuming you have example responses in your API spec, you can set your API to “auto-mock.” When a user tries out a request, SwaggerHub will return the example response from your spec. The response won’t contain the custom parameters the user entered in the UI but will instead return the example responses coded into your spec as if returned from a server.

Providing an auto-mock for your API solves the problem of potentially complicating user data by having users interact with their real API keys and data. In many cases, you don’t want users junking up their data with tests and other experiments. At the same time, you also want to simulate the API response.

Simulating the API can be especially useful for testing your API with beta users. One reason many people code their API with the spec before writing any lines of code (following a spec-first philosophy such as that described by Michael Stowe) is to avoid coding an API with endpoints and responses that users don’t want.

Using the mock server approach, SwaggerHub not only provides documentation but also acts as a beta-testing tool to get the design of your API right before sinking thousands of hours of time into actual coding. You can enable auto-mocking for different versions of your API, creating variants and testing each of the variants.

To set up a mocking server in SwaggerHub, click the plug icon and select to add a new integration. Select the API Auto Mocking service and complete the configuration details. Make sure you have for each of the endpoint responses in your spec. See API Auto Mocking for more details.

Content Re-use (Domains)

Another feature exclusively available in SwaggerHub is the concept of domains. Domains are re-useable code snippets that you can leverage to avoid duplication in your spec.

When you create definitions for your requests and responses, you may find yourself re-using the same code over and over. Rather than duplicating this code, you can save it as a domain. When you want to re-use the code, you select this domain.

Using the domain minimizes duplicate content and enables you to be more consistent and efficient. You can read more in Domains.

Organizations and projects

The collaborative aspect of SwaggerHub is the most common reason people move from the open source tools to SwaggerHub. You might have a lot of different engineers working on a variety of APIs in SwaggerHub. To organize the work, you can group APIs into organizations, and then assign members to the appropriate organization. When that member logs in to SwaggerHub, he or she will see only the organizations to which he or she has access.

Additionally, within an organization, you can further group APIs into different projects. This way teams working in the same organization but on different projects can have visibility into other APIs.

Organization of projects by team

This aspect of organizations and projects may not seem essential if you have just one or two APIs, but consider how you’ll scale and grow as you have dozens of APIs and multiple teams. In these more robust scenarios, the organization and project features become essential.

Expanding the tech writer’s role with APIs

Tech writers are positioned to be power players in the spec-first philosophy with OpenAPI design. By becoming adept at coding the OpenAPI spec and familiar with robust collaborative tools like SwaggerHub, tech writers can lead engineering teams not only through the creation and refinement of the API documentation but also pave the way for beta testing, spec review, client/server SDK generation, and more.

Designing a fully-featured, highly functioning OpenAPI spec is at the heart of this endeavor. Few engineers are familiar with creating these specs, and technical writers who are skilled at both creating the spec and setting up Swagger tooling can fill critical roles on API teams.

Great tools aren’t free. SwaggerHub does cost money, but this is a good thing since free tools are frequently abandoned, poorly maintained, and lack documentation and support. By using a paid tool from a robust API company (the same company that maintains the Swagger tools and sponsors the OpenAPI specification), you can plug into the infrastructure you need to scale your API documentation efforts.

To read more about SwaggerHub, check out my blog post SwaggerHub: A collaborative platform for working on OpenAPI/Swagger specification files, and more.

Related resources

43/153 pages complete. Only 110 more pages to go.

Sours: https://idratherbewriting.com/learnapidoc/pubapis_swaggerhub_smartbear.html

Documentation swaggerhub

SwaggerHub Extension for Visual Studio Code

The SwaggerHub extension lets you view and edit your OpenAPI definitions stored in SwaggerHub directly from Visual Studio Code. You can access your organization's APIs and domains and sync the changes back to SwaggerHub.

Both SwaggerHub SaaS and On-Premise are supported.


  • View and navigate definitions from your SwaggerHub organizations.
  • Edit and save definitions to SwaggerHub.
  • Create new APIs and domains from scratch or using a template.
  • Create new versions of your APIs and domains.
  • Preview your APIs in Swagger UI.
  • Delete definitions by the version or the entire definition.
  • Validate your definitions against the OpenAPI 3.0 and 2.0 schemas.
  • Add API mocks for quick definition testing.


VS Code version 1.50.0 or later.

Get started

1. Configure the extension

Before using the SwaggerHub extension, you need to configure its settings:

Api KeySpecify your SwaggerHub API key found at https://app.swaggerhub.com/settings/apiKey or at if you use SwaggerHub On-Premise.
DestinationIf you use SwaggerHub On-Premise, change the value to . SwaggerHub SaaS users should leave the default value, .
OrgsClick the Edit in settings.json link and specify a list of SwaggerHub organizations that you want to access, as shown in the example below. You can also add your username to the list to access definitions created in your personal account.

2. Load & work with your API definitions

Click SwaggerHub button on the left-hand side to open the SwaggerHub extension. You will see a list of APIs and domains from the connected organizations.

Select an API or domain to view or edit it:

Open an API

The selected definition is downloaded to a temporary folder on your computer. When you save the changes in the editor, the updated definition is uploaded back to SwaggerHub.

Use the extension

Create an API or domain

You can create new API definitions and domains from scratch or using a template. To do this, click plus button at the top of the SwaggerHub APIs or SwaggerHub Domains panels and follow the prompts.

Create an API definition

Create a new version of an API or domain

Open a definition in the editor, change its value, and save the changes. A new version will be created and saved to SwaggerHub.

Create a new version

Set the default version

If an API or domain has several versions, the default version has the full star icon in the list. To make another version the default one, open that version in the editor and select SwaggerHub > Make default from the context menu.

Change the default version

Preview an API in Swagger UI

To see how your API documentation looks in Swagger UI, click Swagger UI in the top right corner of the editor or select SwaggerHub > Preview in Swagger UI from the context menu. The preview is updated automatically as you make changes in the editor.

Swagger UI preview

In Swagger UI, you can also test the requests using Try it out. For this to work, your API definition needs to specify the or (either a live server or a mock server).

Auto Mocking

With SwaggerHub, you can quickly create a mock of your API. Mocks are handy for quick prototyping and integration testing. For more information, see API Auto Mocking in the SwaggerHub documentation.

To create a mock, select SwaggerHub > Add Auto Mocking integration from the editor context menu. The mock server is added to the list or the / keys in your API definition. You can then test the requests and see mock responses in Swagger UI.

Note: SwaggerHub On-Premise users need v. 1.26 to add mocks from within the VS Code extension.

Auto Mocking integration

Change the visibility or status

The visibility (public or private) and status (published or unpublished) of the current definition is displayed in the VS Code status bar. Use the editor context menu to change the visibility and status.

Change status

Check the syntax

The extension checks YAML formatting and validates your definitions against the OpenAPI 3.0 and 2.0 schemas to detect errors such as missing required keywords or misspelled keywords. The number of errors is displayed in the status bar. Click that number to open the Problems view containing the full list of errors, from where you can jump to the corresponding lines in the editor.

Syntax error example

Delete APIs, domains, or versions

Click Close button next to a specific version to delete it. If this is the only version, you will be prompted to delete the entire API or domain.

Delete an API

Reload from SwaggerHub

To reload the list of APIs, domains, and their versions from SwaggerHub, click Refresh button at the top of the list.

You can also reload the version list for a specific definition by clicking refresh button next to it.

Refresh an API


Find and filter APIs and domains

The SwaggerHub APIs and SwaggerHub Domains panels support VS Code's "filter on type" feature to find and filter definitions. Select the top item, then start typing a name to find the matching definitions. Optionally, you can click Enable Filter on Type in the filter box to see only matching definitions.

Filter on Type

Peek definition

To preview the referenced definition inline, right-click the value and select Peek > Peek Definition from the context menu.

Peek a definition

Jump to a reference

To navigate to the referenced definition, Ctrl-click the value or right-click it and select Go to Definition from the context menu.

Go to a definition

Questions and feedback

If you have any questions, suggestions or want to report a bug, please open an issue here:

Sours: https://marketplace.visualstudio.com/items?itemName=SmartBearSoftware.vscode-swaggerhub
SwaggerHub 101: Learning the Basics

SwaggerHub generates interactive API documentation for your OpenAPI definitions. Use it to explore the API endpoints, parameters, responses, and data models, and test the API calls directly in your browser.

Documentation-only view

Click on the SwaggerHub toolbar to view just the API documentation (or domain documentation) without the editor.

Previewing Interactive API Documentation in SwaggerHub

Click the image to enlarge it.

Copy the resulting documentation link and share it with your API consumers who need access to your API documentation.

Note:If your API is private, you will need to add consumers as collaborators with the View role so that they can view your API documentation

API documentation pages follow the same naming format as API and domain pages, but with the suffix added after (or ) in the address:

If you omit the version number, the documentation page will show the default version:

Custom branding

This information applies to SwaggerHub SaaS only.

Organizations can add a custom logo to their API documentation to maintain the company’s brand awareness. The logo will be displayed in the consumer-facing documentation for all of the organization’s APIs and domains. See Docs Branding for details.

Custom logo in API documentation

"Try it out"

Interactive documentation lets you test API calls directly from the browser using the Try it out button. SwaggerHub will show the response headers and body, the request duration, and the cURL command that can be used to send the same request from the command line.

Testing API calls in SwaggerHub

Click the image to enlarge it.

Target server for requests

In order for “try it out” to work, your API definition must specify the (in OpenAPI 2.0) or (in OpenAPI 3.0) so that SwaggerHub knows where to send requests:

If you do not want to use a production server, or if you do not have one yet, you can use SwaggerHub’s mock server. The mock server will generate responses based on the response schemas and examples specified in your API definition.

Routing requests

SwaggerHub lets you send "try it out" requests directly from your browser to the target server, or proxy the requests through the SwaggerHub server. As a rule of thumb, use a browser to access local APIs, and a proxy for Internet-facing APIs.

You can change the routing mode at the bottom of the docs. The selected option is saved in the browser’s and applies to all APIs you test from this browser.

Routing options

Routing requests via SwaggerHub proxy (default)

This is the preferred mode for Internet-facing APIs. "Try it out" requests from the browser are first sent to the SwaggerHub server, which forwards the requests to the target API server. Responses from the API server are sent back to the SwaggerHub server and then to your browser. This approach avoids browser restrictions for cross-domain HTTP requests.

Routing requests via SwaggerHub proxy


  • No need for CORS support on the API server.

  • Supports user-defined parameters in the header.


  • If you use SwaggerHub SaaS, the API server must be on the public Internet and allow connections from our IP addresses. SwaggerHub On-Premise supports both Internet-facing and local servers (except , and ).


  • The request timeout is not configurable and is set to:

    • 30 seconds in SwaggerHub SaaS
    • 30 seconds in SwaggerHub On-Premise 1.21.0 and later
    • 10 seconds in earlier versions of SwaggerHub On-Premise
  • When using SwaggerHub SaaS, "try it out" requests are proxied through the SwaggerHub cloud servers. If privacy or ownership of infrastructure is a concern, use routing via browser instead, or consider using SwaggerHub On-Premise hosted on your own infrastructure.

  • In SwaggerHub On-Premise, requests cannot be sent to , and .

Routing requests via browser

Supported in SwaggerHub SaaS and SwaggerHub On-Premise 1.18.7 and later.

In this mode, "try it out" requests are sent directly from the web page to the API server by using JavaScript.

Routing requests via browser


  • Supports both Internet-facing servers and local servers.

  • Requests are sent directly from your browser to the API server, without going through any intermediate infrastructure.

  • Requests are sent with browser cookies (but not with user-defined cookie parameters).



  • Cannot send requests to HTTP (non-secure) servers from SwaggerHub SaaS and SwaggerHub On-Premise hosted on HTTPS, because the browsers block access to insecure content from secure web pages.

  • Cannot send user-defined values in the header and other forbidden request headers.

  • Response headers displayed after "try it out" are restricted by the response header. If this header is missing, only simple response headers are displayed.

  • The response header is not displayed due to browser security restrictions.

Troubleshooting "try it out" requests

TypeError: Failed to fetch

When routing requests via browser, this error happens if:

  • the API server does not support CORS

  • request is sent from an web page to an (non-secure) server.

To avoid the issue, change the routing mode to Use proxy.

OpenAPI 3.0 specifics

Some features of OpenAPI 3.0 are currently not supported in the Interactive Documentation. See here for known limitations.

Lazy loading

SwaggerHub reduces the documentation load time by loading external references only when they are needed for rendering. See Lazy Loading to learn more.


The API and domain documentation supports permalinks to individual operations, tags, models, and domain components. To get a permalink to a specific item, expand that item, and then copy the full link from the browser address bar:

Permalinks in API documentation

When a user navigates to a permalink, the page automatically scrolls to the target item and expands it. Try it yourself:


Permalinks have the following syntax:

  • For tags and operations:

  • For other items:

Take a look at some examples below:

Link to the tag.
Link to the operation with ID inside the tag.
Link to the model.
Link to the parameter definition in an OpenAPI 2.0 domain.
Link to the parameter definition in an OpenAPI 3.0 domain.

See Also

SwaggerHub Editor
CORS Requirements for "Try It Out"

Sours: https://support.smartbear.com/swaggerhub/docs/ui/interactive-documentation.html

Now discussing:

API Documentation


At Hackney, we believe in working in a collaborative way and this is embedded into our API development process. Before commencing the implementation stage, each API endpoint will first need to be documented using SwaggerHub.

The benefits of this include:

  • Open specification standards.
  • Opportunity to mock the API and avoid possible blockers for front end development.
  • Opportunity to share and reach a common agreement of what the API request and response should look like before any work has commenced.


The documentation aids our collaboration process, as it is shared with the whole team. People, both from technical and non-technical backgrounds, can provide feedback and request changes. This can save hours of development and also ensures that every team member has an understanding of the main question — what will this API do?

We have chosen SwaggerHub as a tool to document our APIs as it contributes to the efficiency of our development process, by giving us a central point of reference, built collaboratively, with a defined objective for the eventual shape of the API.


You can start by watching our overview video:

SwaggerHub is an integrated API development platform that brings together all the core capabilities of the open source Swagger framework, along with additional advanced capabilities to build, document, manage, and deploy your APIs.

SwaggerHub allows us to build an implementation specification, and serves as documentation for the API we are developing. In this way, developers have clearly defined requirements of how the API endpoint they are working on needs to look — this includes request parameters, response object and error responses.

Additionally, we share the API blueprint with other relevant parties, such as the Product Owner, to confirm that the data, that is part of the request and response of the API, is correct, based on the business area understanding of the wider team and any prior discovery work completed. It is a way of getting everyone from the team to work towards the same, shared goal.

Documenting APIs#

The process of documenting API endpoints involves working with a YAML file, where we would specify information such as the path to the API endpoint, the search parameters, API response object, the data types used and whether input fields are mandatory or not.

YAML fileThe YAML fileOpen API generated documentationThe generated documentation

SwaggerHub’s online editor automatically validates the YAML file produced and allows developers to instantly see any changes they make by reflecting them onto the visual representation of the API endpoint. For easy visualisation, SwaggerHub interprets the OpenAPI document as easy to read documentation. This UI clearly lays out the endpoints for the API, which the development team can use for reference when writing code.

Example payload

Models used in the responseThe documentation outlines an example payload and the models which will be used

Documenting the API with SwaggerHub means that we have a consistent specification to follow throughout the development of the API. This is beneficial for the team as we can refer to the swagger docs to confirm that the API is functioning as specified and that the completed API matches the swagger doc specification.

At the end of the project, we can continue to use SwaggerHub as documentation, giving an easy summary of the functions of the API.

Additionally, SwaggerHub provides a way to mock the APIs developed via the tool and make requests against them. This is particularly useful when front end and back end teams are working on the same project. Often, front end work might get blocked as it has a dependency on an API. Providing a mock API and API blueprints will remove this blocker as it will give the front end developers all the information they need to proceed with their work, while back end developers can focus on developing good, reliable and resilient APIs.

This is highly important as it avoids the situation where back-end developers would be rushed to deliver thier work in a quicker manner so that it doesn't block other project work, which may result in lower quality APIs.

Where to find SwaggerHub#

Hackney SwaggerHub is located at https://app.swaggerhub.com/organizations/Hackney.

All the Platform APIs in development have been documented and are viewable on the SwaggerHub.

Sours: https://lbhackney-it.github.io/API-Playbook/documentation/

5420 5421 5422 5423 5424