Last updated

Manage your APIs with the API catalog

No new signups

Looking for Realm documentation? These documentation are for our old developer portal. Realm users should contact their account manager for details of the early access documentation.

The API catalog feature helps you integrate your APIs and files from Redocly API registry into your portal. It also makes it easier to manage multiple versions of APIs in the portal.

The integration flow works as follows:

  1. Upload files to an API in the registry.
  2. Enable your portal to use those files by linking them to the portal configuration.
  3. The portal automatically pulls the files into the project. You can then link to the files from other pages in your portal; for example, insert images into Markdown files or use OpenAPI definitions in portal components.


To use the API catalog in your portal, you need the following:

  • A Redocly Workflows account, with permissions to add new APIs to the registry. Read more about roles and permissions.

  • A Redocly Developer portal project set up and connected to Workflows, with full access to configuration files.

Step 1: Add APIs and files to the registry

In this step, add one or more APIs and any files you want to integrate into the portal to the API registry. Files can be anything: from Markdown pages and images to Redocly-specific configuration files like redocly.yaml or permissions.rbac.yaml.

You can use any API source except URL to add your APIs to the registry. Read more about API version sources.

In this guide, we're referring to GitHub as the recommended source.

Follow the file upload guide to upload files to the registry.

Step 2: Configure the API catalog in the portal

In the previous step, you added APIs to the registry and uploaded some files to one or more API versions.

In this step, collect file links for each version you want to integrate into the portal, and add them to the API catalog.

  1. In the API registry, find and select the API you want to integrate. APIs in the registry are distinguished by their name and version.

  2. On the selected API Overview page, find the branch that contains the files you want to use in the portal. This is either your production (primary) branch, or one of the preview branches.

  3. Select Files link for the branch and save the copied link for later use. The link is in the format If you select a non-primary branch, the link includes the selected branch:

Repeat the procedure for every API version you want to integrate.

  1. In the root of your portal project, create a file called catalog.yaml.

The structure of the catalog.yaml file should be as follows:

# List of APIs from the registry to integrate into the portal. 

  - title: # Optional custom title to use for the API. If omitted, the API name from the registry is used by default.
    defaultVersion: # Optional indicator specifying which of the listed 'versions' to treat as the default. If omitted, the last listed version is treated as the default.
    disableAutoSidebar: # Optional parameter that prevents automatically creating the default 'sidebars.yaml' file. When set, users must manually add files to their existing 'sidebars.yaml' file or include a 'sidebars.yaml' file alongside their registry files.
    pathPrefix: # Optional parameter to specify where to download files. When set, it replaces the automatically created 'api-name' folder. The 'api-version' subfolder(s) will still be created for non-default versions in the specified path prefix.
    versions: # One or more versions of the API to integrate.
      - link: # Must be a 'Files link' for a specific API version in the registry.
  1. Add the file links you've copied to the catalog.yaml file.

Example catalog.yaml

  - title: ACME
    disableAutoSidebar: true
      - link:
  1. Save the changes to the catalog.yaml file and start the portal build.

Import files into the portal

During the portal build, files are automatically downloaded to your portal project. A .gitignore file containing the files is automatically created. To update your files, do not commit or push them directly from the portal project. Instead, upload new versions of files through the registry. When a file is modified in the registry, the portal detects it and automatically triggers a new build.

For the default version, files are downloaded into the api-name folder. For all other versions, files are downloaded into their respective api-name/api-version subfolders. Use the optional pathPrefix parameter in catalog.yaml to set any other path to replace the api-name.

In our examples above:

  • files for ACME would be downloaded into acme, because there's only one version, which is the default, and because we didn't set a custom path prefix.
  • files for Redocly API v1 (default) would be downloaded into /apis/starter/redocly, but files for v2 would be downloaded into /apis/starter/redocly/v2.

For the default version, all files are downloaded, including Markdown files, images, sidebars.yaml (if it exists), and any other configuration files. For non-default versions, only the API definition file is downloaded.

Markdown and MDX files are automatically turned into pages in the portal, and you can link to them from any other page. Similarly, you can include other files (like images) in your existing portal pages.

Use the Redocly configuration file

If a Redocly configuration file exists among the files for the default version and has settings in the theme.openapi section, the portal uses those settings for all versions of an API (default and non-default).

The theme.openapi section supports all Reference configuration options plus two special options for controlling access to content:

  • excludeFromSearch - If set to true, the API documentation is excluded from search results and the sitemap. Default value is false.
  • permission - Defines the permissions using role-based access controls.

Example Redocly configuration file

    root: ./openapi/acme-v1.yaml
        pagination: section
        showConsole: true
        permission: 'read:internal-docs'
        excludeFromSearch: true

Add files to portal sidebar

If a sidebars.yaml file doesn't exist for the default version, it is automatically generated. This default sidebars.yaml contains all files from your registry link. The following example shows the contents of the automatically generated sidebars.yaml file.

- page: ./*

To skip creating the default sidebars.yaml file for an API, set disableAutoSidebar: true on the API level in your catalog.yaml. In this case, you must add the files to a sidebars.yaml file manually, or include a sidebars.yaml file in the registry.

Step 3: Create API catalog page

By default, the portal does not automatically create any catalog page to display your integrated APIs. Redocly provides a few built-in catalog pages in the future. For now, you can use helpers to build it.

The useCatalog helper is experimental, so it may change. We are extending it to support filtering.

Here is an example catalog page called apis.mdx:

title: API Catalog

import { Catalog } from './_components/Catalog';

<Catalog />

Notice that metadata from features.catalog is available in the metadata returned from catalog.