Cumulocity

Cumulocity MQTT Service API

Standards-compliant, multi-tenant MQTT broker for application-level messaging that does not need Cumulocity's domain model. Topics are tenant-scoped, persistent, and bridgeable to the Cumulocity domain model via the Dynamic Mapper. Use it as a general-purpose MQTT broker inside your Cumulocity tenant.

Documentation GitHub

Documentation

📖

Documentation

https://cumulocity.com/docs/device-integration/mqtt-service/

Specifications

⚙

AsyncAPI

https://raw.githubusercontent.com/api-evangelist/cumulocity/refs/heads/main/asyncapi/cumulocity-mqtt-service-asyncapi.yml

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/cumulocity-mqtt-service-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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

AsyncAPI Specification

asyncapi: 2.6.0
info:
  title: Cumulocity MQTT Service
  version: 2025.1
  description: |
    Standards-compliant, multi-tenant MQTT broker for application-level messaging that does not need
    Cumulocity's domain model. Topics are tenant-scoped, persistent, and bridgeable to the Cumulocity
    domain model via the Dynamic Mapper.
servers:
  production:
    url: 'mqtt.{tenant}.cumulocity.com:8883'
    protocol: mqtts
    description: TLS-secured multi-tenant MQTT 5.0 broker.
    variables:
      tenant:
        default: example
    security:
    - basicAuth: []
defaultContentType: application/json
channels:
  '{tenantId}/{topic}':
    description: Tenant-scoped topic hierarchy for arbitrary application messages. Topics are isolated per tenant
      and persisted; subscribers receive missed messages on reconnect when using MQTT 5.0 session expiry.
    parameters:
      tenantId:
        schema: {type: string}
      topic:
        schema: {type: string}
    publish:
      operationId: publishGeneric
      summary: Publish to a tenant-scoped MQTT topic.
      message:
        $ref: '#/components/messages/GenericMessage'
    subscribe:
      operationId: subscribeGeneric
      summary: Subscribe to a tenant-scoped MQTT topic.
      message:
        $ref: '#/components/messages/GenericMessage'
components:
  messages:
    GenericMessage:
      name: genericMessage
      title: Generic MQTT Message
      summary: Arbitrary application payload published on a tenant-scoped topic.
      payload:
        oneOf:
        - type: object
          additionalProperties: true
        - type: string
  securitySchemes:
    basicAuth:
      type: userPassword