June 5, 2026 - Alarm upsert endpoint

Change Log Platform services
, ,
1

Context

Change Type: Feature
Product area: Platform services
Component: REST API
Deployed at: eu.latest.cumulocity.com, apj.cumulocity.com, jp.cumulocity.com

Technical details

Build artifact: cumulocity (2026.165.0)
Internal ID: MTM-66518

Description

Cumulocity now provides a dedicated alarm upsert endpoint (POST /alarm/alarms/upsert).
The operation creates a new alarm if no uncleared alarm with the same source and type exists,
or updates the existing one otherwise. The response status reflects the outcome 201 Created
for a newly created alarm, or 200 OK when an existing alarm was updated.

For details refer to the alarm upsert operation
in the Cumulocity OpenAPI Specification.

1 Like
2

What is not 100% clear to me is how de-duplication is handled here.

For the original POST / CREATE Alarm operation de-duplication logic applies if alarm to same source and type already exists . De-duplication means count is increased but no other data will be changed.

What happens with this new endpoint? It is stated that the alarm is updated in that case, so very simlar to de-duplication but I guess updates of data is acutally reflected, which wasn’t the case in de-duplication, correct?

So I would argue it’s a replacement for the orignal POST endpoint?