Orchestration Cluster API

Name: Orchestration Cluster API API
Brand: Orchestration Cluster API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsProject Managementbearer, basic151 EndpointsREST

For Agents

Drive a Camunda 8 cluster: deploy BPMN and DMN resources, start and search process instances, complete user tasks, publish messages, and resolve incidents.

Quickstart

Get started with Orchestration Cluster API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"start a Camunda process instance"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Orchestration Cluster API API.

Deploy BPMN process and DMN decision definitions to a Camunda 8 cluster via /resources

Start, search, cancel, and modify process instances via /process-instances and /process-instances/search

Claim, assign, and complete user tasks via the /user-tasks resource

Publish messages and signals to running process instances via /messages and /signals

GET STARTED

Start building with Orchestration Cluster API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Orchestration Cluster API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Orchestration Cluster API, keeping it validated and agent-ready. The Camunda 8 Orchestration Cluster API is the REST gateway for interacting with a running Camunda cluster — deploying process and decision definitions, starting and managing process instances, completing user tasks, publishing messages and signals, resolving incidents, and querying audit and job data. The surface covers 151 paths across 35 resources including process-definition, process-instance, user-task, decision-definition, incident, batch-operation, and tenant management.

Use Cases

Patterns agents use Orchestration Cluster API API for, with concrete tasks.

★ Process Orchestration for AI Agent Workflows

Engineering teams encoding multi-step agent workflows in BPMN can use the Orchestration Cluster API to deploy the diagram, start instances when a user request arrives, and complete user tasks as steps finish. The /process-instances and /user-tasks resources expose the lifecycle controls needed to embed Camunda as the durable state machine behind an agent.

POST /process-instances to start a 'customer-onboarding' process with the new customer's email as a variable, then POST to /user-tasks/{userTaskKey}/completion when each manual step is finished.

Incident Monitoring and Recovery

Operations teams monitoring long-running business processes need to spot stuck instances and recover them without manual database edits. The /incidents resource lists open incidents, /incidents/{incidentKey}/resolution clears them once root cause is fixed, and /process-instances/search filters by state to surface processes blocked by incidents.

GET /incidents/search filtered by errorType, resolve each by calling /incidents/{incidentKey}/resolution, and report the count of incidents cleared.

Message Correlation for Event-Driven Processes

Event-driven Camunda processes wait at message catch events until a correlated message arrives. The /messages publication endpoint lets external services push correlation messages by name and key, advancing waiting instances without polling.

POST /messages with name='payment-received' and correlationKey=order-id to advance the matching process instance past its message catch event.

AI Agent Process Workflows via Jentic

Through Jentic, an agent searches for 'start a process instance', loads the input schema for /process-instances, and executes the call without managing bearer or basic credentials. Jentic's vault holds the cluster credential and injects it at execution time, keeping cluster access tightly scoped.

Use the Jentic SDK to search 'start a process instance', load the /process-instances operation schema, and execute it with the BPMN process ID and a variable map.

Key Endpoints

151 endpoints — jentic publishes the only available openapi specification for orchestration cluster api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

POST

/process-instances

Start a new process instance

POST

/process-instances/search

Search for process instances

POST

/user-tasks/search

Search user tasks across the cluster

POST

/messages/publication

Publish a message for correlation

POST

/incidents/search

Search incidents in the cluster

POST

/resources/deployment

Deploy BPMN and DMN resources

POST

/jobs/activation

Activate jobs for an external task worker

POST

/process-instances

Start a new process instance

POST

/process-instances/search

Search for process instances

POST

/user-tasks/search

Search user tasks across the cluster

POST

/messages/publication

Publish a message for correlation

POST

/incidents/search

Search incidents in the cluster

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Camunda cluster credentials (Basic password or Bearer JWT) are stored encrypted in the Jentic vault. Agents receive scoped execution rights and Jentic injects the credential into the Authorization header at call time, so the raw secret never enters the agent's context.

Intent-based discovery

Agents search by intent (for example, 'start a process instance' or 'complete a user task') and Jentic returns the matching Camunda operation along with its input schema, so the agent can call /process-instances or /user-tasks without browsing the docs.

Time to first call

Direct Camunda 8 integration: 2-4 days for auth setup, base URL templating, and async job activation. Through Jentic: under two hours to search, load, and execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

GitHub REST API

GitHub triggers code-driven events that often kick off Camunda workflows for code review, deployment, or release orchestration.

Pair GitHub for source-control triggers with Camunda when an event needs to advance a long-running BPMN workflow.

Complementary

Slack Web API

Slack delivers user-task notifications and approvals back to Camunda processes that wait on human decisions.

Use Slack to notify assignees of pending Camunda user tasks and capture their responses before completing the task.

Complementary

Jira Cloud API

Jira issues frequently represent the human side of work that Camunda processes orchestrate end to end.

Use Jira when a Camunda user task needs an auditable issue artefact for the human assignee to track.

FAQs

Specific to using Orchestration Cluster API API through Jentic.

Why is there no official OpenAPI spec for Orchestration Cluster API?

Camunda does not publish a single consolidated OpenAPI specification for the v2 Orchestration Cluster REST API. Jentic generates and maintains this spec so that AI agents and developers can call Camunda 8 via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Orchestration Cluster API use?

It supports HTTP Basic auth and HTTP Bearer auth with a JWT. Self-managed clusters typically use Basic; Camunda 8 SaaS uses a JWT obtained from its OAuth provider. Through Jentic, the credential is held in the Jentic vault and injected into the Authorization header at execution time so it never enters the agent's prompt context.

Can I start a process instance through Jentic?

Yes. Search 'start a process instance' through the Jentic SDK. Jentic returns POST /process-instances with its input schema. Provide the BPMN processDefinitionKey or processDefinitionId and a variable map to begin execution.

How do I complete a user task assigned to a human?

Call the user-task completion endpoint under /user-tasks/{userTaskKey} with the variables to be set on completion. Use /user-tasks/search first to find the task by assignee, candidate group, or process instance key.

What is the base URL of the API?

The base URL is configurable via server variables: {schema}://{host}:{port}/v2, defaulting to http://localhost:8080/v2 for self-managed clusters. Camunda 8 SaaS replaces these with the cluster-specific gateway URL provided in the Console.

Can the API publish messages to running process instances?

Yes. POST to the /messages publication endpoint with a message name and correlation key. Camunda routes the message to any waiting message catch events in process instances whose correlation key matches.