# How can we add more metadata to Mender's "Check for deployments" response

**URL:** <https://hub.mender.io/t/how-can-we-add-more-metadata-to-menders-check-for-deployments-response/7348>\
**Category:** General Discussions\
**Tags:** mender-server\
**Created:** [November 24, 2024, 3:16pm UTC](https://hub.mender.io/t/how-can-we-add-more-metadata-to-menders-check-for-deployments-response/7348 "2024-11-24T15:16:21Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ch3ckmat3](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/ch3ckmat3/32/2272_2.png) [@ch3ckmat3](https://hub.mender.io/u/ch3ckmat3)\
**Post date:** [November 24, 2024, 3:16pm UTC](https://hub.mender.io/t/how-can-we-add-more-metadata-to-menders-check-for-deployments-response/7348/1 "2024-11-24T15:16:21Z")

</div>

What we currently get from the “check for updates” endpoint `${MENDER_SERVER_URL}/api/devices/v1/deployments/device/deployments/next` is something like this:

```auto
{
    "id": "guid",
    "artifact": {
        "artifact_name": "name",
        "source": {
            "uri": "download_url",
            "expire": "2024-11-14T20:19:18.017488718Z",
            "method": "GET"
        },
        "device_types_compatible": [
            "device_type"
        ]
    }
}

```

What if we want to add more metadata to this response, for example:

- new veriosn of the update
- release notes
- size of the payload (not the artifact, but the update payload)
- hash of the payload

Currently, we can get all this info only after we have downloaded the artiact, and that too is deep inside nested TARs, so you have to do post-processing after download before you can get all this info.

---

<div class="post-metadata">

**Author:** ![TheYoctoJester](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/theyoctojester/32/1444_2.png) [@TheYoctoJester](https://hub.mender.io/u/TheYoctoJester)\
**Post date:** [November 25, 2024, 9:15am UTC](https://hub.mender.io/t/how-can-we-add-more-metadata-to-menders-check-for-deployments-response/7348/2 "2024-11-25T09:15:55Z")

</div>

Hi @ch3ckmat3,

as you mentioned in the other thread that it solved your problem at least well enough for now, should I mark this as solved?

Greetz,  
Josef

---

<div class="post-metadata">

**Author:** ![ch3ckmat3](https://yyz2.discourse-cdn.com/flex036/user_avatar/hub.mender.io/ch3ckmat3/32/2272_2.png) [@ch3ckmat3](https://hub.mender.io/u/ch3ckmat3)\
**Post date:** [November 26, 2024, 2:26pm UTC](https://hub.mender.io/t/how-can-we-add-more-metadata-to-menders-check-for-deployments-response/7348/3 "2024-11-26T14:26:49Z")

</div>

Hi, thank you for the reply.

It kinda does but I am not going to use it for my current application (a Flutter app). If there is no other cleaner way of doing it, I can close this one, but can the Dev team at Mender register it as a featue requeast, as it sure has practicle use cases.