Camunda Services core API
Camunda Services core API as documented publicly: 2 operations. Contract generated from the documentation by API Evangelist (2026-10-06); not the provider's own document.
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/camunda-services:core-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.1.0
info:
title: Camunda Services core API
version: '2026-10-06'
description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-10-06: 2 operation(s) read from 2 public documentation page(s) (each operation
names its page in x-source). This is not the provider''s published contract; Camunda Services has published no machine-readable contract that
the pipeline could find. Engine: local.'
x-evidence-tiers:
code-example: 8
documentation: 14
pages-with-code: 12
pages-read: 23
x-generated-from: documentation
x-provenance: generated
x-authored-by: API Evangelist
x-generated: '2026-10-06'
x-generator: generate-contract-from-docs.py
x-engine: local
x-sources:
- https://docs.camunda.io/docs/guides/getting-started-agentic-orchestration
- https://docs.camunda.io/docs/next/reference/glossary
x-docs-section: core
servers:
- url: https://api.cloud.camunda.io
paths:
/cluster/v2/status:
get:
operationId: get_cluster_v2_status
tags:
- Cluster
summary: GET /cluster/v2/status is deliberately unauthenticated so load balancers can use it as a health check.
x-source: https://docs.camunda.io/docs/next/reference/glossary
responses:
'200':
description: Success (status as documented)
x-evidence:
kind: documentation
/v1/chat/completions:
post:
operationId: post_v1_chat_completions
tags:
- Chat
summary: POST /v1/chat/completions
x-source: https://docs.camunda.io/docs/guides/getting-started-agentic-orchestration
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/PostV1ChatCompletionsRequest'
responses:
'201':
description: Success (status as documented)
x-evidence:
kind: code-example
language: curl
snippet: "curl -X POST http://localhost:11434/v1/chat/completions \\ -H \"Content-Type: application/json\" \\ -d '{\"model\":\"gpt-oss:20b\"\
,\"messages\":[{\"role\":\"user\",\"content\":\"Hello!\"}]}' Configure properties The example blueprint downloaded in step one is\
\ preconfigured to use AWS Bedrock. Update the connector's configuration using the Model provider and Model sections to use Ollama instead.\
\ Model provider \n S"
security:
- bearer: []
components:
schemas:
PostV1ChatCompletionsRequest:
type: object
properties:
model:
type: string
messages:
type: array
items:
type: object
properties:
role:
type: string
content:
type: string
securitySchemes:
bearer:
type: http
scheme: bearer
tags:
- name: Chat
- name: Cluster