Liblab Liblaber API
The Liblaber API from Liblab — 3 operation(s) for liblaber.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/liblab-liblaber-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Liblaber API
version: '2026-10-04'
description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-10-04: 14 operation(s) read from 21 public documentation page(s) (each operation names its page in x-source). This is not the provider''s published contract; Liblab has published no machine-readable contract that the pipeline could find. Engine: local.'
x-evidence-tiers:
code-example: 16
documentation: -2
pages-with-code: 21
pages-read: 21
x-generated-from: documentation
x-provenance: generated
x-authored-by: API Evangelist
x-generated: '2026-10-04'
x-generator: generate-contract-from-docs.py
x-engine: local
x-sources:
- https://liblab.com/docs/tutorials/ci-cd/postman-api/index
- https://liblab.com/docs/tutorials/documentation/docusaurus-enhanced-api/index
- https://liblab.com/docs/howto/fastapi
- https://liblab.com/docs/howto/flask/index
- https://liblab.com/docs/howto/remix/index
- https://liblab.com/docs/howto/aspnet/index
- https://liblab.com/docs/howto/django/index
- https://liblab.com/docs/howto/go-goa/index
- https://liblab.com/docs/howto/nestjs/index
- https://liblab.com/docs/howto/nextjs/index
- https://liblab.com/docs/howto/fastapi/index
- https://liblab.com/docs/howto/fastify/index
- https://liblab.com/docs/howto/go-huma/index
- https://liblab.com/docs/howto/laravel/index
- https://liblab.com/docs/howto/spring-boot/index
- https://liblab.com/docs/tutorials/generate-sdks/sdk-for-fastapi
- https://liblab.com/docs/tutorials/ci-cd/integrate-with-github-actions
- https://liblab.com/docs/tutorials/generate-sdks/sdk-for-fastapi/index
- https://liblab.com/docs/tutorials/ci-cd/integrate-with-github-actions/index
- https://liblab.com/docs/tutorials/ci-cd/integrate-with-gitlab-pipelines/index
- https://liblab.com/docs/tutorials/ci-cd/integrate-with-jenkins-pipelines/index
servers:
- url: https://raw.githubusercontent.com
security:
- apiKey: []
tags:
- name: Liblaber
paths:
/liblaber/control-repo-template/main/Jenkinsfile:
get:
operationId: get_liblaber_control_repo_template_main_Jenkinsfile
tags:
- Liblaber
summary: GET /liblaber/control-repo-template/main/Jenkinsfile
x-source: https://liblab.com/docs/tutorials/ci-cd/integrate-with-jenkins-pipelines/index
responses:
'200':
description: Success (status as documented)
x-evidence:
kind: code-example
language: curl
snippet: "curl --remote-name \"https://raw.githubusercontent.com/liblaber/control-repo-template/main/Jenkinsfile\" \n This command downloads the official liblab Jenkins file ( Jenkinsfile ) and places it in the root of your Control Repo. The Jenkinsfile is a pipeline configuration file for automating SDK generation and pull request creation when specific files or directories, such as liblab.config.json , spec/"
/liblaber/control-repo-template/refs/heads/main/.github/workflows/{liblab-generate-sdks.yaml,liblab-sdk-updates.yaml}:
get:
operationId: get_liblaber_control_repo_template_refs_heads_main_github_workflows_liblab_gener
tags:
- Liblaber
summary: GET /liblaber/control-repo-template/refs/heads/main/.github/workflows/{liblab-ge…
x-source: https://liblab.com/docs/tutorials/ci-cd/integrate-with-github-actions
parameters:
- name: liblab-generate-sdks.yaml,liblab-sdk-updates.yaml
in: path
required: true
schema:
type: string
responses:
'200':
description: Success (status as documented)
x-evidence:
kind: code-example
language: curl
snippet: "curl --create-dirs --remote-name-all --output-dir .github/workflows \"https://raw.githubusercontent.com/liblaber/control-repo-template/refs/heads/main/.github/workflows/{liblab-generate-sdks.yaml,liblab-sdk-updates.yaml}\" \n This command downloads the official liblab GitHub Actions files ( liblab-generate-sdks.yaml and liblab-sdk-updates.yaml ) and places them in the .github/workflows directory of y"
/liblaber/control-repo-template/refs/heads/main/.gitlab-ci.yml:
get:
operationId: get_liblaber_control_repo_template_refs_heads_main_gitlab_ci_yml
tags:
- Liblaber
summary: GET /liblaber/control-repo-template/refs/heads/main/.gitlab-ci.yml
x-source: https://liblab.com/docs/tutorials/ci-cd/integrate-with-gitlab-pipelines/index
responses:
'200':
description: Success (status as documented)
x-evidence:
kind: code-example
language: curl
snippet: "curl --create-dirs --output .gitlab-ci.yml https://raw.githubusercontent.com/liblaber/control-repo-template/refs/heads/main/.gitlab-ci.yml \n This command downloads the official liblab Bitbucket pipeline file ( .gitlab-ci.yml ) and places them in the root of your Control Repo. \n .gitlab-ci.yml This file automates the SDK generation process and creates pull requests for changes in specific files, su"
components:
securitySchemes:
apiKey:
type: apiKey
in: header
name: X-API-Key