liblab.config.json
Liblab configuration file
| Type | object |
|---|---|
| File match |
liblab.config.json
*.liblab.config.json
|
| Schema URL | https://catalog.lintel.tools/schemas/schemastore/liblab-config-json/latest.json |
| Source | https://cdn.jsdelivr.net/npm/liblab@latest/liblab.config.schema.json |
Validate with Lintel
npx @lintel/lintel check
The liblab Configuration File
Properties
A local relative path to your specification file or a publicly reachable URL to the spec file
The list of languages you want to generate SDKs for
The name of your SDK
version of your API
name of your API
Should developer documentation be generated? docs are supported for: java, python and typescript
The workflow configuration
2 nested properties
A local relative path to your arrazo specification file or a publicly reachable URL to the arrazo spec file
The desired output name for the workflow
Should API documentation or code snippets be generated?
Customizations to SDKs
18 nested properties
{}
5 nested properties
1 nested properties
The prefix to use for the access authentication
1 nested properties
The header to use for the api key authentication
1 nested properties
1 nested properties
The prefix to use for the custom authentication
5 nested properties
Enable oauth authentication
Use basic authentication for the oauth token
The security scheme definition for the oauth
The buffer time in milliseconds before the token expires to refresh it
2 nested properties
1 nested properties
The format of the documentation code snippets
2 nested properties
Name of the output file, will default to enhancedApiSpec.json
Whether to include OAuth endpoints in the enhanced API documentation. Note that the SDK handles calling these endpoints.
Should example dev container files be generated?
Customizations for specific endpoints
Should example .env files be generated?
toggles whether optional parameters are included in code snippets in generated SDK documentation.
Should the SDKs infer service names?
A list of all custom models paths
Optional configuration for licensing the SDKs
2 nested properties
What license should the SDKs be covered under?
URL for a CUSTOM license
The parameters for the refresh token system
3 nested properties
The key to use for the bearer token
The endpoint to use for refreshing the token
The key to use for the refresh token
Should the SDKs return a response with both the data and headers?
Should unreferenced models be built?
Retry functionality customization
8 nested properties
How long should the SDKs wait between attempts in milliseconds?
What is the exponent base used to calulate wait times?
Should the SDKs include retry behavior?
What HTTP codes should the SDKs retry on?
What HTTP methods should the SDKs retry on?
How many attempts should the SDKs make before giving up?
What is the maximum time between attempts in milliseconds?
What is the maximum random jitter applied to wait times in milliseconds?
1 nested properties
Overwrites the SDK README description
1 nested properties
Whether to include deprecated operations in the SDKs
The Base URL of your SDK
Language specific options
9 nested properties
C# specific options
12 nested properties
The PackageId of your C# SDK. It identifies your NuGet package.
Enable Optional
Enable response validation to check for missing required fields and invalid null values
The list of authors who contribute to the SDK (In TypeScript the first is the only one displayed)
The name of the Github Repo that will be Pull Requested to
List of files that shouldn't be produced by liblab, used for when you want to keep specific files safe from changes
The version of the liblab SDK Generator
renames all model properties with illegal names, during the SDK generation
The version of the SDK
The target to branch off from when opening a PR, if not specified will default to main branch
go specific options
11 nested properties
The name of the go module
Additional variables to include in the constructor and access in the hooks
The list of authors who contribute to the SDK (In TypeScript the first is the only one displayed)
The name of the Github Repo that will be Pull Requested to
List of files that shouldn't be produced by liblab, used for when you want to keep specific files safe from changes
The version of the liblab SDK Generator
renames all model properties with illegal names, during the SDK generation
The version of the SDK
The target to branch off from when opening a PR, if not specified will default to main branch
Java specific options
15 nested properties
The groupId of the Java package
The name of the Java package
The artifactId of the Java package
Include Kotlin snippets and documentation in the generated SDK
The developers' information to add to pom.xml for project association
Additional variables to include in the constructor and access in the hooks
The list of authors who contribute to the SDK (In TypeScript the first is the only one displayed)
The name of the Github Repo that will be Pull Requested to
List of files that shouldn't be produced by liblab, used for when you want to keep specific files safe from changes
The version of the liblab SDK Generator
renames all model properties with illegal names, during the SDK generation
The version of the SDK
The target to branch off from when opening a PR, if not specified will default to main branch
Python specific options
16 nested properties
Should the Python SDK enforce request validation?
Additional variables to include in the constructor and access in the hooks
The name of the Python project
Should the version be strict?
The list of authors who contribute to the SDK (In TypeScript the first is the only one displayed)
The name of the Github Repo that will be Pull Requested to
List of files that shouldn't be produced by liblab, used for when you want to keep specific files safe from changes
The version of the liblab SDK Generator
renames all model properties with illegal names, during the SDK generation
The version of the SDK
The target to branch off from when opening a PR, if not specified will default to main branch
PHP specific options
11 nested properties
The name of the composer package
Additional variables to include in the constructor and access in the hooks
The list of authors who contribute to the SDK (In TypeScript the first is the only one displayed)
The name of the Github Repo that will be Pull Requested to
List of files that shouldn't be produced by liblab, used for when you want to keep specific files safe from changes
The version of the liblab SDK Generator
renames all model properties with illegal names, during the SDK generation
The version of the SDK
The target to branch off from when opening a PR, if not specified will default to main branch
Swift specific options
9 nested properties
The list of authors who contribute to the SDK (In TypeScript the first is the only one displayed)
The name of the Github Repo that will be Pull Requested to
List of files that shouldn't be produced by liblab, used for when you want to keep specific files safe from changes
The version of the liblab SDK Generator
renames all model properties with illegal names, during the SDK generation
The version of the SDK
The target to branch off from when opening a PR, if not specified will default to main branch
terraform provider specific options
15 nested properties
The name of the go module used in the terraform provider module
The name of the terraform provider module
The version of the terraform provider module
Should the terraform provider hide computed diff? Default is false
Should the terraform provider mock acceptance tests? Default is true
2 nested properties
The list of authors who contribute to the SDK (In TypeScript the first is the only one displayed)
The name of the Github Repo that will be Pull Requested to
List of files that shouldn't be produced by liblab, used for when you want to keep specific files safe from changes
The version of the liblab SDK Generator
renames all model properties with illegal names, during the SDK generation
The version of the SDK
The target to branch off from when opening a PR, if not specified will default to main branch
TypeScript specific options
18 nested properties
Should the SDKs be bundled?
Should the SDK mark common models with the Common postfix? (Useful when conflicts occur)
Should the SDK export the main class as default?
The HTTP client to use
The NPM package name to publish to
The NPM organization to publish to
Additional variables to include in the constructor and access in the hooks
The list of authors who contribute to the SDK (In TypeScript the first is the only one displayed)
The name of the Github Repo that will be Pull Requested to
List of files that shouldn't be produced by liblab, used for when you want to keep specific files safe from changes
The version of the liblab SDK Generator
renames all model properties with illegal names, during the SDK generation
The version of the SDK
The target to branch off from when opening a PR, if not specified will default to main branch
TypeScript specific options
18 nested properties
Should the SDKs be bundled?
Should the SDK mark common models with the Common postfix? (Useful when conflicts occur)
Should the SDK export the main class as default?
The HTTP client to use
The NPM package name to publish to
The NPM organization to publish to
Additional variables to include in the constructor and access in the hooks
The list of authors who contribute to the SDK (In TypeScript the first is the only one displayed)
The name of the Github Repo that will be Pull Requested to
List of files that shouldn't be produced by liblab, used for when you want to keep specific files safe from changes
The version of the liblab SDK Generator
renames all model properties with illegal names, during the SDK generation
The version of the SDK
The target to branch off from when opening a PR, if not specified will default to main branch
MCP server options
1 nested properties
Should mcp server be generated?
The version of the liblab SDK Generator
Publishing options
1 nested properties
The GitHub organization to publish to
1 nested properties
API documentation integration object
6 nested properties
The name of the Github Repo that will be Pull Requested to
Selecting the provider will enable the liblab service to generate the required files for your integration provider
The target to branch off from when opening a PR, if not specified will default to main branch
1 nested properties
1 nested properties
1 nested properties
Selecting the languages to enhance and include in the mintlify integration. The selected languages will override the languages shown in the mintlify UI.