Skip to main content

Core SDK options

The core SDK options configure the basic settings, such as the location of the spec to use, the SDK languages to generate, and the authentication type to use. These options are set at the top level of the liblab config file.

sdkNamestring1N/AThe name of the SDK
baseUrlstring""The base URL of the API
specFilePathstringN/AThe path to the API spec, either a local path or a URL
languagesarray["python", "typescript"]The list of languages to generate SDKs for
autharrayNoneThe type of authentication to use
createDocsboolfalseShould developer documentation be generated?
customizationsobjectN/ACustomizations to SDKs. See the SDK customization options documentation for more details
languageOptionsobjectN/ALanguage specific options for the SDKs. See the SDK language options documentation for more details
publishingobjectN/APublishing options for the SDKs. See the SDK publishing options documentation for more details
validationsToIgnorearrayN/AA list of API spec validations to ignore. See the API spec validations options documentation for more details

1 sdkName is required if your spec file doesn't have the title set. See the sdkName section for more information.


The sdkName is used to set the name for your SDK. This name is used for the package name for the different SDKs, it is used to name the class that provides SDK access, and is used in the README and other documentation.

This name will be re-cased to be idiomatic for the SDK language. For example - if you set the sdkName to Exciting-Soda:

"sdkName": "Exciting-Soda"

You will get the following:

The SDK will be in TypeScript package called excitingsoda. The class you would use to access the SDK would be called ExcitingSoda:

import { ExcitingSoda } from 'excitingsoda';

const sdk = new ExcitingSoda();

If this is not set, the SDK name is taken from the title field in your API spec.

"openapi": "3.1.0",
"info": {
"title": "ExcitingSoda",

If the title is also not set, the liblab build command will raise an error.


The baseUrl is the URL for your API. If this is not set, the SDK defaults to using first value that is found in the servers object of your API spec.

Java SDK group Id

For Java SDKs, the baseUrl is also used as the group Id, unless you set the groupId language customization option. For example if you have:

"baseUrl": "https://exciting.soda"

Then your Java group Id will be soda.exciting:

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns=""

This can be accessed from the soda.exciting package:

package soda.exciting;

public class ExcitingSoda {

You can read more about configuring URLs and setting these at run time in our URLs and environments guide.


The specFile is the path or URL of your spec file. This can be a local file, or a remote URL. For remote URLs, the liblab CLI will need to be able to access this file, so it will need to be public.

The spec file can be in JSON or YAML format. See our supported API specifications document for more information on the supported spec formats.


The languages setting is an array of the languages you want to generate SDKs for. You can find a list of the supported languages in our SDK language support document.

"languages": [

Language specific customizations can be set in the languageOptions section of the config file.

If this setting is not set, the SDKs will be generated for all supported languages.


The auth setting defines the type of authentication used by your API. This setting is optional, and if not set, the SDKs will not include any authentication.

"auth": [

Valid values are:

apikeyAPI key authentication
basicBasic authentication
bearerBearer token authentication

You can have multiple values if your API supports multiple authentication types.

You can read more on authentication in our authentication guide.


The createDocs setting is a boolean that determines whether or not to generate documentation for your SDKs. Set this true to automatically generate docs, or false (the default) to skip this step.

"createDocs": true

You can read more about documentation generation in our documentation generation guide.