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).