liblab helps you automatically generate SDKs in different programming languages as well as developer documentation for your API. This guide will help you get started, giving you an overview of liblab, the CLI, and the process to generate SDKs.
liblab is currently in beta. Sign up now to get started with our beta.
The SDK generation process
To generate SDKs you use the liblab CLI - a command line interface that has features including the ability to configure and generate SDKs. This CLI takes a configuration file and an API spec, and outputs SDKs and documentation.
The config file is a JSON file that configures the SDK generation. It includes information such as the name of the SDK, the programming language, the API spec file to use, how your API authenticates, and more. The liblab CLI takes this config file, verifies it and your spec, then generates an SDK and documentation. You can find out more about the config file in our config file guide.
The usual developer flow is to work through this process manually a few times to ensure your spec is correct, and that your configuration file is correctly set up for your needs. After this, you can automate the process via your CI/CD pipeline.
Install the liblab CLI
The liblab CLI can be installed using NPM:
npm install -g liblab
You can read more on installation in our CLI installation guide.
Register or login
liblab login command to either register with liblab, or to log in:
You can read more on the registration and log in process in our CLI authentication guide.
You are now ready to generate SDKs using liblab 🎉. Head to our Generate an SDK from your OpenAPI spec guide to generate your first SDK from an OpenAPI spec you already have.
To learn more about the CLI and the configuration file, check out the CLI documentation.
Otherwise, check out one of our hands-on tutorials to help you get started.