Breaking change

Description

• The cloudName fields (and its alias cloud) are deprecated across ITCare APIs.

• Definitive removal: end of November 2026.

• Only cloudId remains guaranteed over time. To get a cloud's name: GET /clouds/{cloudId} → name field.

Why this change ?

• A cloud's name is duplicated across many responses, even though it can be renamed.

• Some endpoints already return a cloud name that is out of sync with the reference value.

• Centralizing the name on a single endpoint removes these discrepancies.

How to migrate ?

BEFORE  →  item.cloudName   (or item.cloud)
AFTER   →  item.cloudId     then   GET /clouds/{cloudId}.name

• Identify every place in your code that reads cloudName / cloud

• Keep cloudId as the reference

• Resolve the name via GET /clouds/{cloudId}

• Recommendation: cache the cloudId → name mapping client-side (the name rarely changes), rather than calling once per item

• Deploy before end of November 2026

Replacement endpoint

GET /clouds/{cloudId}

{
  "cloudId": 12345,
  "name": "MY-CLOUD"
}

• cloudId: stable identifier, present in all the responses listed below.

• name: reference name, unique and always up to date.

Impacted endpoints — by domain

Only endpoints exposing the cloud's name are listed. cloudId remains available and unchanged everywhere.

Compute

Method	Endpoint	Exposed name field
GET	/compute/resources	cloudName
GET	/compute/resources/{id}	cloudName
GET	/compute/platform/resources-obsolescence	cloudName
GET	/compute/backup-policies	cloudName
GET	/compute/backup-policies/{id}	cloudName
GET	/compute/services	cloud
GET	/compute/services/{id}	cloud
GET	/compute/services/{id}/resources	cloudName
GET	/ai/departments	cloudName
GET	/networking/networks	cloud
GET	/analytics/matomo	cloudName
GET	/analytics/matomo/{id}	cloudName

Monitoring

Method	Endpoint	Exposed name field
GET	/monitoring/indicators	cloudName
POST	/monitoring/indicators	cloudName
GET	/monitoring/indicators/{id}	cloudName

Search

Method	Endpoint	Exposed name field
GET	/search	cloudName
GET	/resources	cloudName

Changes

Method	Endpoint	Exposed name field
GET	/changes	cloudName
GET	/patch-parties/{id}/resources/clouds	cloudName
GET	/patch-parties/{id}/clouds	cloudName

Points of attention

• Two field names to handle: cloudName on most endpoints, alias cloud on /compute/services, /compute/services/{id} and /networking/networks.

• POST endpoints (/monitoring/indicators, /api/rfcs/{id}/cis) also return the name in their response — not just GETs.

• Filtering remains based on cloudId (no filter by cloud name is available).

Timeline

Step	Deadline
Publication of this page	Immediate
Migration period	Until end of November 2026
Removal of cloudName / cloud	End of November 2026

FAQ / Contact

For any question or migration support, contact your cegedim.cloud Service Delivery Manager (SDM).