push

Introduction

Redocly Workflows integrates with popular version control services and uses them as the source of your API definitions to help you automatically validate, build, and deploy API reference docs and developer portals. This approach requires you to give Redocly Workflows access to your repositories.

The Redocly CLI push command helps you automate API definition updates without granting Redocly Workflows access to your repositories. This is useful when you can't or don't want to grant Redocly Workflows permissions to your repositories, or when your API definitions are generated automatically from code annotations in a CI/CD pipeline

This allows you to:

• Benefit from using Redocly Workflows to preview documentation and portal builds.
• Manage versions in the API registry.

Apart from uploading your API definition file, the push command can automatically upload other files if they are detected or referenced in the API definition:

• the Redocly configuration file and any configuration files referenced in the extends list.
• the package.json file (if it exists) from the folder where you're executing the push command. Redocly Workflows will use the @redocly/cli version specified in package.json .
• the HTML template and the full contents of the folder specified as the theme > openapi > htmlTemplate parameter in the Redocly configuration file.

By default, the push command only updates an existing API definition version. If an API with the provided name and version doesn't exist in your organization, it will not be created automatically. For details on how to create an API, check the Upsert an API with push section.

Prerequisites

Before using the push command, ensure the following prerequisites are met:

1. Active user account in a Redocly Workflows organization.
2. Active personal API key or organization API key .

Authentication

To authenticate to the API registry, you can use several approaches:

• use the login command . In this case, the command will look as follows:
  Copy

  Copied

  redocly login
  redocly push ...

  Refer to the login command documentation for more details.

• set the REDOCLY_AUTHORIZATION environment variable to either your personal API key or to an organization-wide API key (configurable by organization owners in Redocly Workflows > Settings > API keys ). In this case, the command may look as follows:
  Copy

  Copied

  REDOCLY_AUTHORIZATION=yourPersonalApiKey redocly push ...

  Treat the API keys as secrets and work with them accordingly. Consult the documentation for your CI system to learn more about handling secrets:

  • Travis CI documentation
  • CircleCI documentation
  • GitHub Actions documentation
  • Jenkins documentation

Usage

redocly push [api] <destination>
redocly push
redocly push [-u] [--batch-id id] [--batch-size number] <path/to/definition.yaml> <@organization-id/api-name@api-version> [--branch]

Options

Examples

The command behaves differently depending on the options you pass to it and whether the configuration file exists in your working directory.

You can choose any of the following approaches:

• Specify all options explicitly in the command
• Set options in the Redocly configuration file

Destination

To properly push your API definition to the Redocly API registry, you need the following information:

• Organization ID
• API name
• API version

Pass this information to the push command in the following format: @organization-id/api-name@api-version.

Organization ID

The push command uses the following order of precedence: first, it takes the organization ID from command-line arguments (if provided). If the organization ID is not provided explicitly, it takes it from the configuration file.

To find your organization ID required for the command:

1. Log into Workflows.
2. Access the API registry page.
3. In your browser's address bar, find the URL of this page.
4. Inspect the segment after app.redocly.com/org/ . This part is your organization ID.

For example, if the URL is app.redocly.com/org/test_docs, the organization ID is test_docs. When using the push command, you would provide this ID as @test_docs.

API name

To find your API name required for the command:

1. Log into Workflows.
2. Access the API registry page.
3. Check the list of APIs displayed on this page.
4. Inspect the title of each list item to the left of the New version and Edit API action buttons. This title is an API name.

When using the push command, you would provide the API name after the Organization ID separated with the forward slash (/). For example: @test_docs/petstore-api.

API version

To find your API version required for the command:

1. Log into Workflows.
2. Access the API registry page.
3. Check the list of APIs displayed on this page.
4. Inspect the subtitle of each list item to the bottom of the API name . This subtitle is an API version.

When using the push command, you would provide the API version after the API name separated with the "at" symbol (@). For example: @test_docs/petstore-api@v1.

Set options explicitly

Provide the api as a path to the root API definition file, and specify the organization ID, API name and version.

redocly push openapi/petstore.yaml @openapi-org/petstore-api@v1

In this case, push will upload only the definition that was passed to the command. The configuration file is ignored.

To push the definition to a particular branch, specify the branch name.

redocly push openapi/petstore.yaml @openapi-org/petstore-api@v1 -b develop

Set options in the configuration file

Depending on the contents of your Redocly configuration file, you can use simplified push syntax instead of providing the full path to the API definition file.

Example configuration file

organization: organization-id
apis:
  api-name@api-version:
    root: path/to/root/definition.yaml
  another-api:
    root: openapi/openapi.yaml

With a configuration file like this, you can use any of the following commands:

1. redocly push

Push every API listed in the apis section of the configuration file. You must specify your Workflows organization ID in the configuration file for this approach to work. APIs without an explicitly defined version are automatically pushed to @latest.

2. redocly push api-name@api-version

Push the specified API and version from the apis section of the configuration file. You must specify your organization ID in the configuration file for this approach to work.

3. redocly push organization-id/api-name@api-version

Push the specified API and version from the apis section of the configuration file to the Workflows organization matching the provided organization ID. In this case, you don't have to specify the organization ID in the configuration file.

Upsert an API with push

To upsert an API in the registry with the push command, use the --upsert or -u option.

redocly push -u test-api-v1.yaml @redocly/test-api@v1

redocly push -u test-api@v1

redocly push -u

To upsert the definition to a particular branch, specify the branch name with --branch or -b.

redocly push openapi/petstore.yaml @openapi-org/petstore-api@v1 -b develop

redocly push -u test-api@v1 -b develop

Batch ID

The --batch-id option can be used by Redocly Workflows to associate multiple pushes with a single CI job.

Below are possible use cases for the --batch-id option:

• CI/CD systems: group pushes from a single CI job together so that each push does not trigger separate reference docs/portals rebuild.
• External systems: a parameter that can be used in reports, metrics, analytics to refer to a specific application service state.

Must be used only in combination with the --batch-size option.

Batch Size

The --batch-size option can be used by Redocly Workflows to understand how many pushes in total will be performed within one batch to properly handle parallel pushes.

Must be used only in combination with the --batch-id option. Must be an integer bigger than 1.

Skip decorator

You may want to skip specific decorators upon running the command.

redocly push openapi/petstore.yaml @openapi-org/petstore-api@v1 --skip-decorator=test/remove-internal-operations

redocly push openapi/petstore.yaml @openapi-org/petstore-api@v1 --skip-decorator=test/remove-internal-operations --skip-decorator=test/remove-internal-schemas

Public

The --public option allows you to upload your API definition and make it publicly accessible from the API Registry. By default, definitions uploaded with the push command are not available to the public. For more information on how to configure access to your APIs, check the registry access section.

redocly push openapi/petstore.yaml @openapi-org/petstore-api@v1 --public

Files

The --files option allows you to upload other folders and files.

redocly push openapi/petstore.yaml @openapi-org/petstore-api@v1 --files ./path/to/folder

You can also add files and folders providing them in .redocly.yaml:

apis:
  main: 
     root: ./openapi.yam;
files:
  - ./path/to/folder
  - ./path/to/another-folder/file.md
  - ./file.md

--files has bigger priority than .redocly.yaml

Set up CI from Redocly Workflows

The Redocly Workflows interface can help you get started with the push command.

1. In API registry , select Add API .
2. In the Definition name step, provide a name for your new API definition.
3. In the Choose source step, select Upload from CI/CD . This generates syntax for the push command that you can copy and use to upload a new API definition file. Or use the redocly push -u command directly from the command-line interface.

Learn more

• Video tutorial: Using the Redocly CLI push command: