Liberate Orchestration Platform API

HTTP interface for triggering Liberate workflows. A workflow is started with a PUT request carrying a bearer token, a flow slug, and a JSON context object. Every customer receives their own unique endpoint URL plus separate QA and production environments; the exact curl invocation for a given workflow is published in the properties of that workflow's Start Event. Flows may be synchronous (the end output is returned as the response) or asynchronous (an immediate status code and instance ID are returned while long-running or human-in-the-loop steps continue).

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.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/orchestration"
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.

API entry from apis.yml

apis.yml Raw ↑
aid: liberate:orchestration
name: Liberate Orchestration Platform API
description: HTTP interface for triggering Liberate workflows. A workflow is started with a PUT request
  carrying a bearer token, a flow slug, and a JSON context object. Every customer receives their own unique
  endpoint URL plus separate QA and production environments; the exact curl invocation for a given workflow
  is published in the properties of that workflow's Start Event. Flows may be synchronous (the end output
  is returned as the response) or asynchronous (an immediate status code and instance ID are returned
  while long-running or human-in-the-loop steps continue).
humanURL: https://docs.liberateinc.com/docs/calling-a-workflow
baseURL: https://integration.liberateinc.io
tags:
- Workflow Orchestration
- Automation
- Insurance
properties:
- type: Documentation
  url: https://docs.liberateinc.com/docs/overview
- type: GettingStarted
  url: https://docs.liberateinc.com/docs/calling-a-workflow
- type: Authentication
  url: authentication/liberate-authentication.yml