Get Started

The following sections explain important concepts and prerequisites for first-time users.

Read these sections to get started with SwaggerHub Portal.

Prerequisites

You need the following prerequisites to get started with SwaggerHub Portal:

  • Software as a service (SaaS) enterprise plan with SwaggerHub.

  • One of the following organization-level roles in the connected SwaggerHub organization:

    • Designer

    • Owner

Trial and Purchase

SwaggerHub Portal is available for use in conjunction with SwaggerHub. You can trial SwaggerHub Portal as a new and existing SwaggerHub customers. The SwaggerHub Portal trial period lasts for 14 days (On-prem is 30 days). For additional information, contact our Sales Team.

If you wish to use SwaggerHub Portal after the trial period ends, contact our Sales Team to:

  • Purchase the product.

  • Extend the trial period.

Products

A SwaggerHub Portal product contains the following resources:

  • APIs. One or more API definitions, linked from the respective SwaggerHub organization. APIs are always maintained in SwaggerHub.

  • Documentation. Pages explaining how to interact with the APIs. Pages are created in Markdown language. The page editor in SwaggerHub Portal features a graphical user interface, also known as a What You See Is What You Get (WYSIWYG) editor.

Portal Status

SwaggerHub Portal allows you to set one of the following statuses:

  • Portal online. This status means that you can access both the provider view and the consumer view. Both providers and consumers can access and navigate your published portal when it is online.

  • Portal offline. This status means that you can only access the provider view. Opening the consumer view returns an offline message. Providers and consumers cannot access your published portal when it is offline.

You can change the visibility status of your portal anytime.

SwaggerHub Portal Concepts

SwaggerHub Portal uses the following concepts and hierarchy:

  • A provider or consumer is a member of a SwaggerHub organization.

  • A SwaggerHub organization can have one associated portal.

  • A portal contains one or more products.

  • A product contains:

    • One or more linked APIs.

    • One or more documentation pages explaining how to consume the linked API or APIs.

portal_concept_hierarchy_PA5.png

Example Concept Hierarchy for SwaggerHub Portal

Publication date: