ConnectCloud Developers

ConnectCloud API

The ConnectCloud API gives your software the same access to a ConnectCloud tenant that people have in the portal: create and work on desk tickets, read employees and absences, record working time, send notifications through your own mail and webhook channels, and react to events.

This is the documentation for developers and integrators. If you are looking for how to use ConnectCloud, see the user documentation.

How the API is organised

ConnectCloud is a set of modules. Every module has its own versioned REST API under the API host https://api.mbcom.cloud (see Environments):

Module Base path What it covers
HR /api/hr/v1 Employees, roles and groups, absences, working time, organisation. Also issues the access tokens for every API.
Desk /api/desk/v1 Tickets, issues and tasks with configurable spaces, types, workflows and fields; comments, mail, SLAs, automation, projects and payment plans (work is booked in HR).
Forge /api/forge/v1 Software development: projects with repositories, items (APP-12), milestones, iterations, views, automations, ownerships and teams (code ownership); handoff and conversion with desk.
Work entries /api/hr/v1/work-entries Book work (Leistungen) with start/end or a stopwatch, approvals, rates and billing batches (HR).
Comms /api/comms/v1 Mail and webhook channels, delivery log, inbound webhooks (notifications about events are flows).
Trade /api/trade/v1 Offers, orders, invoices, credit notes, contracts, purchase orders, inbound invoices.
DMS /api/dms/v1 Documents with versions, folders, links to records, text extraction, containers, compliance, exports.
Master data /api/masterdata Addresses (customers, suppliers) with contacts, articles, product groups, lookup tables, number ranges.
CRM /api/crm/v1 Leads, campaigns, opportunities, customer satisfaction, address quality checks.
Workflow /api/workflow/v1 Approval workflows: blueprints, a person's tasks, running instances.
Flows /api/flows/v1 Automation: flows as YAML (triggers, module actions, conditions, human tasks, mail, AI), test runs, publishing, runs, the task inbox and inbound webhooks.
Search /api/search/v1 Full-text search over desk, CRM, master data, trade, knowledge, HR and comms records and DMS documents.
Status /api/status/v1 Whether the modules of the environment are working (no token needed).

All APIs share the basics: JSON over HTTPS, the same bearer tokens and an error object with an error message. HR, Desk, Comms and Forge also share stable error codes, optimistic locking and rate limits; where another module differs, its reference page says so in its Conventions section.

Start here

  1. Quickstart: from an API key to your first call in five minutes.
  2. Authentication: API keys, service accounts, access tokens and permissions.
  3. Sandbox: try every endpoint against example data, no account needed.
  4. The API reference per module (for example Desk or DMS): every endpoint with parameters, schemas, examples and a Try it console.

Guides per module

Module Guides
HR Work entries, Careers API
Desk Tickets, Projects, plans and billing, Handoff and conversion
Forge Items: project configuration, create, search, workflow by status category; Handoff and conversion
Trade Sales documents and e-invoices: offers, orders, invoices, XRechnung, inbound invoices, 423 workflow_locked
Master data Addresses and articles: codes, addresses, articles, sync with paging and change detection
CRM Leads and opportunities: duplicates, conversion into a customer, pipeline stages
DMS Documents: upload, folders, malware scan, versions, download
Flows Flows
Comms Mail, channels and the delivery log, Webhooks

Machine-readable descriptions

  • OpenAPI 3.1 documents per module, e.g. /openapi/desk.yaml (also as .json; the index lists all of them). Use them to generate clients or import them into Postman, Insomnia or Bruno.
  • For AI agents: /llms.txt, /llms-full.txt, a Markdown version of every page and an MCP server at https://developers.mbcom.cloud/mcp. See AI agents.

Scope

The reference lists the endpoints API clients may use. Routes that only the portal itself or other ConnectCloud services call (sign-in flows, internal service APIs, the customer portal) are not part of the public API and may change without notice.

View as Markdown