Skip to main content

CLI Overview

The liblab CLI is used to generate SDKs from your API specs. This can be run from your terminal or as part of your CI/CD pipeline.

As a developer generating SDKs from an API, your typical flow might be:

The typical CLI flow. 1 - Install the CLI. 2 - Register or log in. 3 - Initialize the config file. 4 - optionally validate your spec and build hooks. 5 - generate the SDK and docs. 6 - publish the SDK and docs. The typical CLI flow. 1 - Install the CLI. 2 - Register or log in. 3 - Initialize the config file. 4 - optionally validate your spec and build hooks. 5 - generate the SDK and docs. 6 - publish the SDK and docs.

If you are integrating the CLI into your CI/CD pipeline, your typical flow might be:

The typical CLI flow. 1 - Install the CLI. 2 - Register or log in. 3 - Initialize the config file. 4 - optionally validate your spec and build hooks. 5 - generate the SDK and docs. 6 - publish the SDK and docs. The typical CLI flow. 1 - Install the CLI. 2 - Register or log in. 3 - Initialize the config file. 4 - optionally validate your spec and build hooks. 5 - generate the SDK and docs. 6 - publish the SDK and docs.

You can find tutorials walking you through different areas of this flow in our tutorials.

Use the liblab CLI​

info

You can get a list of all the available commands by running liblab --help:

liblab --help

You can also get help on individual commands by running the command with --help. For example:

liblab build --help
Last updated on