# Alerts API inconsistency

**URL:** <https://community.developer.atlassian.com/t/alerts-api-inconsistency/92982>\
**Category:** JSM Cloud\
**Tags:** jira-cloud, rest-api\
**Created:** [June 13, 2025, 4:04pm UTC](https://community.developer.atlassian.com/t/alerts-api-inconsistency/92982 "2025-06-13T16:04:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ArtemMiroshnychenko](https://avatars.discourse-cdn.com/v4/letter/a/a9adbd/32.png) [@ArtemMiroshnychenko](https://community.developer.atlassian.com/u/ArtemMiroshnychenko)\
**Post date:** [June 13, 2025, 4:04pm UTC](https://community.developer.atlassian.com/t/alerts-api-inconsistency/92982/1 "2025-06-13T16:04:35Z")

</div>

Hello, there is some kind of misunderstanding regarding the Alerts API. [The documentation](https://developer.atlassian.com/cloud/jira/service-desk-ops/rest/v2/api-group-alerts/#api-v1-alerts-get) says that there is the “extraProperties” field must be included in the response:

```auto
     "extraProperties": {
        "backend": false,
        "browser": "Firefox 113.0",
        "browser.name": "Firefox",
        "bundler": "parcel@2.10.3",
        "environment": "production"
      },...

```

What I actually see:

```auto
curl --request GET \
--url 'https ://api.atlassian.com/jsm/ops/api/{cloudId}/v1/alerts?&query=detailsPair:(cluster!:production)&from=1749729674000&to=1749816177000
--user 'me:token' \
--header 'Accept: application/json'

{
"values": [
{
"id": "XXXXX",
"tinyId": "16154",
"createdAt": "2025-06-13T12:00:49.789Z",
"updatedAt": "2025-06-13T12:10:49.463Z",
"message": "[Prometheus]: NodeCPUHighUsage [info] prometheus — High CPU usage.",
"entity": "",
"source": "/alertmanager...",
"status": "closed",
"alias": "d3df7763768dca848174830d930bfd6fb1d661f276d362641c9f66b52aeb20f2",
"tags": [],
"acknowledged": false,
"count": 1,
"owner": "",
"snoozed": false,
"lastOccuredAt": "2025-06-13T12:00:49.789Z",
"integrationType": "Prometheus",
"integrationName": "SRE-prometheus",
"priority": "P4",
"responders": [
{
"id": "xxx",
"type": "team"
}
],
"actions": [],
"seen": true
},
...

```

The field extraProperties is included only if I query the alert by its ID, using the **Get Alert** API.

I’ve also come across [this issue](https://jira.atlassian.com/browse/JSDCLOUD-15138), but for some reason, it was closed without any explanations.

If I have, let’s say, 100 alerts and I want to make a digest of non-critical alerts, I would have to make 100 separate API calls to get the information about each alert. Why is there a discrepancy between the documentation and the actual API? ☹  
Thanks for any advice.

---

<div class="post-metadata">

**Author:** ![GeorgeArmfield](https://avatars.discourse-cdn.com/v4/letter/g/8edcca/32.png) [@GeorgeArmfield](https://community.developer.atlassian.com/u/GeorgeArmfield)\
**Post date:** [September 30, 2025, 6:25am UTC](https://community.developer.atlassian.com/t/alerts-api-inconsistency/92982/2 "2025-09-30T06:25:13Z")

</div>

I’ve been trying to get my extra properties showing for hours just to finally find this thread… Come on Jira… Very frustrating and the ticket got closed with 0 communication: [[JSDCLOUD-15138] List Alerts endpoint is not returning extraProperties - Create and track feature requests for Atlassian products.](https://jira.atlassian.com/browse/JSDCLOUD-15138)